skysight-inc/HackerNews huggingface dataset:
> Everything about our society will be decided by the people with the most money if people accept anonymous currencies. Democracy isn't possible when you can't hope to detect when influence is being purchased.

Traceable currency doesn't solve that problem. People don't have to use literal money to buy influence. The politician does what you want and you make sure their kid gets into the right college. Or you hire their son in law at $250K/year. Or you run advertising that isn't officially part of their campaign but helps them stay in office. Or refrain from running critical advertising.

The problem is not proving that each transaction took place. It's proving that one was a quid pro quo for another. Which the currency tells you nothing about.

> If I know someone is buying influence and I want to reject their power to do so, I can stop accepting any money they've used in that way.

And if you're one person or ten people then nothing happens. But if you have a sufficiently powerful coalition with an organizational structure capable of causing the coalition to act in unison then you become the tyranny of the majority and it is the minority who needs protecting from you.
Thanks for the suggestions -- looking into them now. Clever idea to sign up for a site's weekly email instead of skimming the site.

I used to sign up for an HN newsletter that'd only show the top posts. I thought that was an effective way of pushing only the best content to me every few days. Realized later that I enjoy reading a some articles that didn't get a lot of upvotes.

I also tried to create an open google doc where a small group of friends could share links to articles they found particularly noteworthy. Participation was 0, so I gave up and now just store interesting articles in my bookmarks folder. Messy.
What about Go gets you excited where Rust doesn't?
Their product IS terrible. Remember they actually charge users for this unlike other networks that monetize purely from advertising. LinkedIn can and should be far better but it's incredibly how bad it really is.
nope, diesel is yellow. never seen a green fuel can.
Just today I wondered why are so few journalists picking up the fact that ISIS is using almost exclusively archive.org for uploading their beheading and other PR videos.
This is undoubtedly interesting content for writers and bloggers. I'll think on it and PM you if I come up with anything worthwhile.
I'll take your word for it. I'm no gas can expert. :)
> The recruiter's real customer is not really any one particular candidate, who they might see just once in their whole career, but the employer, who will likely be a repeat customer if the recruiter satisfies their needs.

And I'm cool with that. Recruiters do an important job for me at the point in my career that I'm at. Cut through the bullshit. I don't want to deal with a wishy-washy employer. I don't want it to be my whiny voice they hear asking them for more money.

I want a buffer. Because if there's one thing I know about corporations it's that there's a lot of stupid thinking going around when it comes to hiring. Employers think they want things when the things they want, once they had, they'll realize they didn't really want that, and you're the one that has to pay the price for that. Using a recruiter means you're serious about hiring.

I want to stay in my own little world and just code. Job hunting is stressful. I'm happy to let the recruiter do the stressful parts for me. Far as I'm concerned it's a fair trade.
I would argue that 'Refactoring' gives you a bunch of tools for discovering your good abstractions. Whereas GoF puts a bunch of ideas in your head without giving you any preparation for using them responsibly.
I'm interested if some of those guarantees can be used upstream in rust-postgres?

As far as I saw, Diesel is essentially shipping with its own PostgreSQL driver.
Sure, but it's not like we're all keeping records of cash transactions for the mandarins to go through later when they become annoyed.
It sure would be nice if everything was working according to the standards :-)
It's not that surprising. Animal husbandry quite plausibly predates civilization, let alone labs / theory / written records.
It's possible. I tried to build on rust-postgres originally, but its design basically makes it impossible to abstract over. We also have fundamentally different views on how `ToSql` should work.
Progressive Enhancement with the WordPress REST API
Blog claims Alpine is based around being secure and light weight...but gives no indication on why it is secure. Oh, lightweight because of busy box? Is there scrutiny on packages installed? I don't see the security component.

Maybe Docker can reveal more there, though given how they iterate and things break, I'm not sure they are willing (or capable).
Software Engineer 5 at Facebook is total comp $268k on glassdoor. Your estimates are way too high.
I really hope someday we get spambots that start off by trying to make useful contributions. Then later, after building a following, start advertising scams.

I'm confident that, given the right incentives, spam kings could discover conversational AI before any lab.
Got in close to the bottom with the QQQ in 2009. Chickened out and thought we'd reached a top in 2013 and cashed out. Was sitting in cash for 2 years.

Now I believe we're going down. I'm shorting through options to get some bigger action. 3x from SQQQ not good enough- so buying 6-12 month puts on Cloud companies and QQQ. Didn't get in it at the top - started at about 10% below the top.
Real programming ended with Mel.
It was the Loebner Prize actually. Which is a much, much weaker test than the one Turing imagined in his original imitation game paper.
The Plot to Steal the Color White from DuPont
For the record, that's not how it works at DO. The support department encompasses Platform Support (like T1), Trust & Safety (handles cases of possible fraud or abuse complaints), and CloudOps (sysadmins who help maintain the cloud).

I'm on Platform Support and while I can't access the actual hypervisor hardware like CloudOps can, we do not have "scripts", and we always do our best to help customers in any way we can. We also have a myriad of tools that we can use to monitor our platform and help troubleshoot any issues that may arise in our tickets.

My roommate and bestie is on CloudOps, and she sits right next to me at our HQ in NYC. While we have a great remote culture, all of us on support are in the US, with the exception of one guy in London (who started last week and is AWESOME).

Not only that, but I work very closely with all of the other departments here at DO, and our executives are extremely accessible as well. If we need to pass on feedback, we always do so.

We're also encouraged to go out of scope and do whatever possible to help out our customers, and I wouldn't change a thing. I love what I do, I love the people I help, and I love my coworkers.
Hopefully such systems won't be doing a fair amount of dynamic query generation... vs simple pre-baked CRUD operations.
It's an interesting analogy. I would say the customer is in the stronger position and while granted a rare bird has negotiating power - that means the employer is ultimately in the stronger position of the employer/employee relationship.
+1

It seems like the intersection of good use case for Rust and need to use SQL, will also intersect with "minimal SQL needs", hence preference for simpler libraries.
That is pure nostalgia talking. I strongly suspect that if you did you would be appalled and want to switch back after only a few searches. Search in 2016 is leaps and bounds beyond what it was in 2006.
Do you pay tableau $1000 per business report?
The 2 things that create the most beef about PHP are simply:

1. Type Safety (string? int? boolean?)

2. The Runtime Engine (apache? nginx? linux? windows? what file system?)

The flexible nature of these two concepts, leaves any given PHP script resting on shifting sands of uncertainty, which is really the only thing that leaves people feeling inadequate. The willingness to compromise, and accept a runtime where it's hard to debug, permits programmers to put themselves in situations where they'll have a hard time providing a conclusive answer in succinct terms, to non-technical folks disinterested in obscure details beyond the scope of one's external field or daily interests.

It's not because of impostor syndrome, or any sort of psychological underdog complex. It's simply the awareness that there are gaps in what's often expected to be a hermetic seal. And knowing about that, would gnaw at the edges of just about anybody's confidence at a subliminal level.
I think that Rust is substantially harder than Go. At least extrapolating from my personal experience and the 6+ highly-skilled people I've watched learn both Go and Scala simultaneously.
I'd argue that it's a lack of professionalism that's the real problem. It's easy to negotiate yourself out of a perfectly good job offer if you don't know what you're doing. And lets be honest, most devs haven't the slightest clue how to do salary negotiations. Someone posted Patrick's guide, and that's a good start, but you need to learn a whole bunch of little lessons about the corporate world before you can really start to apply them effectively.

Until then, why not just work for market rate or just slightly below? Don't stress yourself out, there's no reason to and it'll hurt your bargaining position. 90% of it is done before you even get to the table anyway.
I hope so. Their whole angle seems to be 'automatic access via proximity'
That page is 9.2MB. Would've been smart to have a landing page or paginate.
I like Brian Eno's Discreet Music [1], which provides three slowed-down variations on Johann Pachelbel's Canon in D Major (the first one rather amusingly named Fullness of Wind), eventually reaching tempos where you can hardly discern the original melody.

Max Richter also brilliantly "recomposed" Vivaldi a few years ago, turning his Four Seasons into something like a modern work.

[1] https://en.wikipedia.org/wiki/Discreet_Music

[2] https://en.wikipedia.org/wiki/Max_Richter#Recomposed_by_Max_...
This is the case whenever your expected salary gets higher than younger, cheaper replacements are willing to accept. This isn't a problem for people that have made more of their younger years, since the positions they're applying for are high enough leverage positions to justify the higher salary ask and younger workers are simply not qualified to apply.

I see this all the time in applicants. They've spent 15-20 years on the job and have less than 5 years of useful experience. The rest is stagnation where they haven't grown their skills. And yet they expect to be paid as if they've got 15-20 years of useful experience. That's why answering the salary question derails the negotiation. There may be an odd recruiter that is willing to accept the premise that an older worker is able to complete the job's tasks at enough above the acceptable level to justify the increase in cost. But most will opt for a younger worker willing to do an acceptable job.
Devicemapper works (make sure you don't use loop devices) okay. Unfortunately it's slow to warm up, but it's probably the most tested storage driver (it's the default on a bunch of systems).

btrfs works pretty well and is quite a bit faster. It's the default for SLE and openSUSE (as well as other distros which use btrfs by default). I'd recommend it (but I can't remember if it requires you to use btrfs on your / partition, which might be an issue for you).

ZFS, while being an awesome filesystem, I doubt has had much testing under Docker, so I'd be wary about using it.

And I've already told you what I thought about overlay. I'd like to point out that it's a good filesystem for what it was designed for (persistent or transient livecds) but the hacks in Docker in order to use it for their layering keeps me up at night.
Court rules Dept. of Justice must explain withheld documents
Nope. But if you work out costs, I think you'll find a dedicated developer on a contract may well work out the same amount as you spend on licensing.
Awesome work. I saw when you announced it on r/thesimpsons. What do you think of Josh Weinstein getting such a kick out of this on Twitter?

Also please give the text a slight drop shadow, if possible.

Ps. This makes me so happy. Thank you for making it.
Immortality Quest Aims to Preserve Brain 100 Years
In the context of my original post: 1) garbage collection, which isn't a big deal for most server applications and 2) simplicity, where the complexity of Rust only buys me marginal performance of questionable utility for the sorts of use cases where I'd be talking to a SQL database.
Is it able to do everything the client software can do?
Indiegogo lays off some employees in restructuring
TL;DR people who are unemployed aren't willing to take less than 100,000 a year and feel like the system is screwing them?

Off topic, but I've said I won't answer it because of commercial in confidence reasons before.
Telemarketers I tend to just say, "No thanks" and hang up on them. They are in a crap job, probably forced into it my circumstance, so the compassionate side of me doesn't want to abuse them.

The argument that wasting their time will ultimately make it uneconomical for those who employ telemarketers is an interesting one, although I doubt we'd get enough critical mass to make a difference. Implementing a basic income so people don't _have_ to work as telemarketers would be better for society as a whole.

On the other hand, the calls from, "Microsoft Security" are actively trying to harm me, so I'll waste their time all I can, delaying their opportunity with the next person.
I'd love to find out what made it impossible to abstract over?

Please include in your larger talk!
Advanced space propulsion startup shuts down
It asks for the widest string in pixels in a proportional font, so the different letters matter.
Diesel's selling point isn't actually the performance aspect. It's the safety and productivity.
Remember those silly cheap <$5 picture frames you find in $2 shops, or as a free bonus online sometimes? You probably have one lying around.

If it uses an AX206 chipset, you can flash whatever code you like onto them with an SDCC-based toolchain.

You get a color LCD with at least 128x128 resolution (some cool devices are 320x320), and MENU, LEFT and RIGHT keys for input. Perhaps best of all, they have a bootloader, meaning burning the wrong code into Flash is completely recoverable :D

There are a couple basic firmware images that come with the toolchain - one to let you control the LCD from Linux, and one that dumps CPU registers in real time (for debugging) - so it's very easy to get started.

Vague high-level overview: http://picframe.spritesserver.nl/wiki/index.php/DPF_with_App...

SVN repo: http://sourceforge.net/p/dpf-ax/code/HEAD/tree/trunk/src/

If you have a device and want to play with this, I recommend cloning the SVN repo and pouring over the readme file inside, which covers backing up your stock firmware, identifying your device model so you know which firmware to build (and if it's an AX206 at all - moment of truth :P), and reflashing. It only takes about 30 minutes to feel like you've read everything thoroughly enough and execute a reflash.

There are some conflicting bits of information and link-rot here and there, but I'll say this: I know zero about low-level device hacking, and I managed to get this installed onto a cheap picture frame I had lying around within a few minutes. I also managed to fully recover from a bad flash run too.

My DPF currently sits on my bedside table with the debug firmware on it (you enable the debug code via a config file change); the sole reason I've done nothing with it (tetris! breakout! space invaders!! :D) is that the buttons on mine are on the back :( (why??? >.>)

So, the project and code actually does do what it says on the tin, and the hardware is very resilient. :D

Note that some picture frames are based on the ST2205u or ST2203u, which use a 6502 core (the AX206 uses a MCS-51 aka 8051 core). This is quite different, with no SDCC toolchain; you'll need to know 6502 asm for these, I think. There does appear to be some LCD-control firmware available for these which you could work from but the AX206 is much easier to start with I think.
Mentioned below where?

If you're talking about query string construction performance, I'm not sure I've ever seen even a Ruby application where query string building was a bottleneck vs the network.
Show HN: Quitter.se – federated Twitter clone
From the article
> 2. Security is improved as the image has a smaller footprint thus making the attack surface also smaller

Not saying you need to agree with that. But that does appear to be at least an "indication"
I like writing Rust for more reasons that CPU efficiency.

In fact, that's behind: strong memory safety, Option/no-null (probably lumps in with "strong memory safety") and of course generics and the type system at large.

The speed is honestly a nice benefit. (I'm not being sassy, I don't have speed intensive applications and still reach for Rust).
Myth Busters CPU vs GPU. Go to 2:40 and 8:00 in the video.

https://www.youtube.com/watch?v=XcolCeWIcss
The short version is its refusal to box things means that you have to have the connection, the statement, and the cursor all as local variables in the same lexical scope (you almost always want to abstract away the statement and cursor), and it's use of trait objects for serialization and deserialization.
I might go into it briefly in my talk, but I don't like to rag on other people's work so I probably won't say much on it.

(Sorry for the double post, I think I replied to my own comment and not yours!)
Sorry, as you replied I had deleted my comment, because I decided I'd rather not get into an argument about this :) I will give you the link though:

https://news.ycombinator.com/item?id=11045700 <- "Diesel performs 33% faster than rust-postgres, and will be competitive with if not faster than ideomatic C. "
Yes problem were people. Too much politics and that's why I left.

Why more data? In case of IP geolocation neither of that technology understood IPs not to mention being able to create a proper index for ranges.

So in case of Mongo, to get a good performance they decided to generate every possible IPv4 address and map it to zip code. To increase efficiency they stored every IP as a 64 bit integer.

In Coherence they did the same thing, but I guess less efficiently (did not look how it was done, since at the time coherence was in the process of being eliminated) I'm guessing maybe they stored is as a string?

Also note that Coherence is a distributed cache that supposed to withstand couple nodes going down, so a lot of data was duplicated.
We're not going to settle the dynamic vs static debate in this thread, so I'll refrain from commenting on safety and productivity :-)

Anyway, I don't mean to dump on your work. It seems like it's actually quite a nice implementation. I'm just questioning 1) the size of the audience and 2) Whether or not the audience who thinks they want this should actually want this.
Government-impervious money transfer as a human right is nebulous at best. The internet has not changed the legal or ethical status of money laundering. At best you could say it has always been a human right, but it's certainly never existed in the US or Western Europe.

Cash transactions carry substantial risk: both parties must be physically present in some place to make the deal. They can be tailed, the meeting place can be under surveillance, they can be raided, they can murder each other and run, etc. It's also impractical to deal with large amounts of cash due to the risk of robbery/theft (including civil forfeiture), and legitimate entities won't take suitcases full of cash for large purchases. Infiltrating and exfiltrating large amounts of money from the legitimate banking system is also very likely to leave traces that can be understood by sufficiently skilled/motivated forensic accountants.

Whereas flipping some bytes in the firehose of cryptographically secure bytes already coming in and out of every home is undetectable and basically risk-free.

Some much more concrete human rights are ensured through taxation: food, shelter, water, health care, police, education, national defense, etc. If you make taxation effectively optional by running a perfect, free money-laundering system, some of them may have to go.
Your observation on abstraction is interesting. I've always considered PHP to be quite the opposite.

e.g. Going from PHP to NodeJS, NodeJS is a lot more direct and less abstracted (handling the request directly, reading the request data incrementally and handling reader state, setting headers and then explicitly writing to the buffer, handling connection state, etc.) - note I do mean NodeJS here, not something like Express

another e.g. PSR-7 I find is, counterintuitively, actually much less abstracted than raw PHP built-ins as it goes out if it's way to map the interfaces to the stack as intended, rather than completely arbitrary weird abstractions. Like the retrieval of query parameters being entirely separate and unrelated to retrieval of the body payload, whereas PHP tends to sort of conflate these things in $_GET/$_POST/$_REQUEST and then doesn't really have obvious intuitive handling of non-x-form-url-encoded payloads. And don't get me started on query string array handling.

I do completely agree with the article though, and I still use PHP a lot. Voluntarily.

But I just found your specific observation surprising.
Oh my. I recall reading this years ago. I had totally forgotten that Eric basically tells Linus to grow up and learn to use version control. Now we're all using Linus' version control.
If you run tableau in an enterprise environment you will likely have a lot of c level executives, global sales teams and more relying on tableau to be available outside of your local business hours. This means any maintenance needs to be planned and communications sent out to all stakeholders.

If reloading was an option then there wouldn't be downtime, and I wouldn't need to schedule a maintenance window for something as simple as updating an email address. The idea being that if there is a config error during a reload, the system just continues uninterrupted with the original config. If I have to stop the system completely in order to run the config sanity checks when it starts again, the potential for prolonged downtime is much greater.
Certainly a lot of hate for Linkedin here - curious, what would people like Linkedin to become? Or what would it take for a new service to be interesting? And given that people are unlikely to pay for a service like this means that advertising and recruiter services are likely the only sources of revenue - are you comfortable with that?

The opportunity I'm surprised Linkedin has not tackled is to create their own CRM system. I think they are the only company that can really challenge Salesforce.com. Imagine getting a CRM system and having everyone in already - a marketing/sales dream. I imagine they thought of this, but may have said it was beyond the pail as it may have driven users away. Interestingly, Hubspot's CRM was offered with data.

To me, the most interesting part of the announcement was highlighted here:

http://adage.com/article/digital/linkedin-shuts-ad-network-1...

They're shutting down their external ad network that they purchased when they bought Bizo. Having tried this product, I'm not surprised - it was a piece of sh*t.
Tell that to the people who debug new CSP/BSPs using binary search on "which line did the boot sequence make it to" using GPIO to an LED.

Thankfully, most of us don't spend a lot of time doing that sort of thing these days (even in the embedded world).

I also feel for anyone who ends up using an upside-down air can to debug shoddy solder joints on a BGA device ;)