skysight-inc/HackerNews huggingface dataset:
If you support Ubuntu, it's trivial to extend that to Debian. Ubuntu is still very tightly pinned to Debian.
One of our (US) employers pays about 10% - 15% of our combined total compensation (read: salary plus "other personnel expenses") for a $250 deductible health insurance plan. And that's just the insurance premium. Dental is extra. 20% co-pay. Bills are always a surprise and full of errors. Sometimes the same service is coded in radically different ways, leading to claim denials and hundreds of dollars of variation in what's billed. It can take six months for a provider to get paid. People here routinely finance life-preserving medical treatment using credit cards. The per-practice administrative overhead for dealing with private insurance claims is estimated by quite a few (peer-reviewed) papers at between 15% and 30%.

If the wrong one of us changes jobs, all of this comes crashing down and I'm back to reading 200-page policies, figuring out what network I'm now in, and trying to determine if I can still see my normal doctor.

15% of after-tax income for no-questions-asked health care, sans any form of billing, sounds like a utopia to me.
I was under the impression that wasn't the case, there's always something, or more accurately, many somethings working together that cause degradation of the system to the point of failure. Are you saying at some point some major organ like the heart just decides to stop beating?
Agree with the points. While billing hourly & tracking time on my own I tend to keep going back to the timer application to pause or start for every small occasion, depending whether I am working on the project or doing something else, even if its for a minute or two, coz distractions are omni-present & I can not work on something straight for 60 minutes at a time. That actually increases my anxiety.

So I much prefer to bill per work/project basis as a whole.

One thing regarding ethics, sometimes a client will want to 'copy' a feature they saw on another website, including the visual feature as well. That makes me uncomfortable, I try to make variations of it, although I have never denied work for this reason. May be next time I will atleast object strongly when its a blatant copy.
People don't die of "nothing". When it's said that someone dies of old age, there's still some actual medical cause (although no one is demanding an autopsy to find it when an 85 year old dies peacefully in their sleep).
No thanks, I don't want to play your games.
Is there a lot of C++ to go traffic ? I have not seen much along those lines. Go doesn't remotely look like a language that a C++ programmer would be interested in. Given its limitation go is an ok enough language but that's about it.
Oh, I see. Thanks for the correction.
Here is my thought.

First of all for debugging it is a huge help to get as rich data back as you can from the other end and logged.

As for the proper handling of exceptions, I think there are a number of semantic attributes that an exception can have: for instance, transient/permanent, and the scope of the exception (is the whole system hosed? just this record? etc.)

In a greenfield application you can build an exception hierarchy that records this, but in the real world it is necessary to build a system that does some inference, or even guessing, to decide what to do about a failure.

I just remember the bad old days when C programs would return an int and it would be -1 if the function failed, or maybe they set errno, and either way you could double the size of some functions if you add in error checking and probably get it wrong.

Exceptions on the other hand are good for the normal kind of call stack and also work in "callback hell" situations since you can stuff them in a field or collection, pass them as a function method, etc.
The situations where roads are better:

- low amounts of people (or goods)
- going into different directions
- coming from different places

The situations where rails are better:

- high amounts of people (or goods)
- going into the same general direction
- coming from the same general area

Which is why roads are damn useful in rural cases, but if you think about building a 23-lane highway, maybe rail might be better.
When people choose to build on a more esoteric language such as Elixir (and to lesser extent Erlang) is it because what they want to do simply is not possible in Ruby/Python/Go/JavaScript/etc or just less efficient, elegant, productive, etc?
It's more a public safety thing than anything else, a drunk guy is going to set his neighborhood on fire make no doubt about it, but the answer to that is the severely punish the drunk flamer not to regulate the actions of responsible people.

I find it funny for a population (HN) that tends to have a anarchist/libertarian bent, that if we so much get the smell of firearms or weaponry we start heading left fast. At some point you have to accept that the world is a dangerous place and the solution to that danger is not to nanny the crap out of people but rather to punish the irresponsible as an example to the potentially irresponsible.
No, you can use phoenix without any javascript, it'll serve up regular html pages just fine. You only need the js if you plan on using sockets to connect to Phoenix's endpoints.
>Is there a way to escape the echo chambers?

So far I haven't found a reliable way out. Social media and personal blogs definitely aren't it. In fact, they're feeding the badness.

Interestingly, I feel that paper editions of newspapers and magazines have less broken articles than their websites.

For me, the scary thing isn't that there are biases. It's that pretty much all major media outlets occasionally participate in Culture Wars™. That is, they take an extreme position on some polarizing issue -- whichever appeals to most of their core audience -- and then use every method available to reinforce their "side" and either ignore or try to discredit the "opposition".

But even that isn't the worst of it. The core problem is that both "sides" of such issues are often objectively wrong. Is it even sensible to try extract The Truth™ from two equally full buckets of bullshit?

I feel like this has become much worse recently. Maybe it's just me changing. Then again, there were no Twitter outrage campaigns before Twitter. There were normal outrage campaigns, but they were mostly wars by proxy fought mostly in the media. People observed them and maybe agreed. Right now, almost everyone is an active participant. Which generates news in its own right and skews coverage even more.
Medium's latest app store update
like working on arc?
Best Articles – Idle Times
You don't deserve the downvotes, but I'm still not sure what your concern is. The modern history of the programming languages ecosystem is marked by rapid specialization and fragmentation, in which 5% market share is an enormous quantity. Furthermore, relative percentage of mindshare isn't as interesting as absolute numbers: your language needs only enough active contributors to keep pace with the evolving trends of the industry, which can likely be achieved with less than 20,000 active users (well less than 1% marketshare).

The point of any given programming language is not to be crowned queen of the programming prom, it's to produce useful software and improve the state of software development. As long as your language meets a minimum threshold for notoriety (which both Go and Rust do), the fact that they have less marketshare than Java is irrelevant unless your sole motivation for learning a language is to get a job at an enterprise company (which is a fine reason to learn a language, but I think you might be on the wrong forum if that's your overriding concern :P ).
No, we wouldn’t scream for a plugin making that possible, but we’d scream for a web standard.

We already have a way to transmit two-way video live in browsers (WebRTC).

It should be not to hard to use the codecs existing for that to make a one-way live streaming in browsers.
People don't just die of "nothing" ... it's just that the death is natural and we don't bother investigating. But, usually, it's one of these that kills old people:

http://seniorhealth.about.com/od/deathanddying/tp/cause_deat...
This analysis doesn't include the cost of the infrastructure to support the full time employee: rent for office space, computer equipment, IT support, etc. None of these costs would be incurred directly by the employer if they hired an independent contractor who worked remotely. So they're definitely part of the overhead cost of a full time employee. (They're also not fixed costs - the amount of office space you need to rent depends on the number of people you employ. So the cost of office space is definitely part the the cost of hiring an employee.)

Strangely, the article accounts for three paid sick days per employee, but not for paid vacation days or holidays, which most employees receive. These are also something the company would pay the cost of for an employee but not for a independent contractor (who only bills for the actual number of working days).
Ecto isn't an ORM since Elixir isn't OO. Terminology aside, Ecto identifies more as an Integrated Query Language in a similar vein as LINQ does in the .NET ecosystem.

As someone who has used lots of ORMs I find the switch to a libary like Ecto very refreshing. It has an intuitive and very composable querying API and friendly DSLs for defining schemas and validations. These are the baseline features of any database/modeling library and Ecto satisfies them nicely.

But by far my favorite feature that has come in handy is that Ecto's concept of Repos does not couple you to a specific database. Unlike traditional ORMs that couple your objects to a specific database (read: the my_cool_app database in MySQL or Postgres) it's easy to support different databases within the same type of RDBMS or different RDBMS entirely. Since all querying in Ecto goes through Repo modules all you need to do is just create more Repo modules and configure them accordingly.

For some people this feature might not sound useful but if you've ever worked on an Enterprise or older app with multiple data sources or want to switch from MySQL to Postgres, this is a killer feature. Doing this with Rails' ActiveRecord is ugly, buggy, a pain and will bring you to your knees during Rails upgrades any time there are major changes in ActiveRecord.
I would be quite interested in understanding why people find death terrifying. I'm likely in a minority, but I look forward to death. That doesn't mean I'm suicidal. It means that I view death as an important moment in my life, one that will force me to measure whether I'm satisfied with the way I lived my life. I'll no doubt have regrets, but I'll have smiles too. I could say that being a person of faith may influence my looking forward to death, but I imagine that even if I wasn't a person of faith, I'd still have a similar mindset. I am very curious why people would want to live forever on this earth. It seems like it'd become quite dreary and boring, especially if I gradually lose control over all my normal physical and mental functions.
Submitted, updated etc would probably benefit from time as well as date.

API endpoints for custom clients would be nice
Just wrote something on [sending errors by emails](http://reganmian.net/). The full code is here: https://github.com/houshuang/survey, including my job module https://github.com/houshuang/survey/blob/master/lib/job_work.... The code worked well for me, mostly because it registers errors and retries (I had problems with rate-limiting of Amazon SES), however it's not parallel right now. I will probably rewrite it to have a single module that gets tasks from the DB, and then dispatches it to workers, and I want to split it out into a separate library.

Note that this was my first Elixir library and I was very much learning as I went along. Lot's of code that I want to refactor and extract.
Nice list! Thanks for compiling!
OP is asking about the phoenix web page, not phoenix itself.
That sounds right. And there are some other technical things, I think, like the ability to bring a lawsuit (though not, of course, the ability to win one on the merits).
I never said it made sense ;-)
Not really, though it's more in the direction we'd need. At around 120, humans seem to die of "systemic failure of the everything". Replacing one part won't suffice; to live past about 120, you either need to replace biology completely, or repair some of its fundamental systemic mechanisms.
How to Attain Financial Independence via the Strenuous Life
2400+SICK+?+DEEMED+FIT+DIED+AFTER+BENIFIT+WITHDRAWN+-+YouTube
Closest thing would have to be new user accounts, but then the analogy definitely falls apart since you can't just double the size of your QA team and check each account before it goes to market. The security issues aren't remotely so well contained.
Ask HN: Are your cloud provider's costs significant?
Should cost be an important factor when choosing a cloud provider for a young startup ?
The article addresses Gompertz' law: the probability of dying in any given year increases exponentially with age (older people have ever higher death rates). This is an EMPIRICAL FACT. As you live longer, this probability accumulates exponentially, so the probability of being alive falls super-exponentially: p(being alive) = aexp(-exp(bt)).

I'm pretty sure there ain't nothing you can do about this. Why not? Because evolution built it pretty strongly into our genes. Here's how I see it: if an organism arose which had this "death gene" turned off, it would not adapt to sudden changes in the environment. It might be susceptible to a novel infectious agent which wipes out the whole species. Thus evolution tends to weed out immortal or very long-lived organisms.

Don't forget how natural selection works. It's not single creatures that adapt; it's about whole species. The only way for a species to adapt is for some of its individuals to die and be replaced by their offspring which differ genetically from their parents.

Evolution needs death to work. Hence death is built-in.

Look at this scary graph (with a logarithmic y axis!):

https://en.wikipedia.org/wiki/Gompertz%E2%80%93Makeham_law_o...

and then tell me that medical advances will do anything to make you live to 200. Go on, I dare ya.
I'm pretty sure the author is referring to the shift in distribution (the movement of the curve), not that medical advances will one day make us able to live past 130 (otherwise the whole point is moot).
I've heard that. I haven't ever had them and can't speak personal from experience, but I've heard from a couple docs that cantharidin works really well, and cryotherapy ranges from might-work to total-garbage. Only downside is the whole "high potential for toxicity and misuse" thing; apparently people have taken cantharidin internally as a supposed aphrodisiac, which is clearly a terrible thing to do with a blistering agent.
If you ran a search engine, what would your search results page for "chicago hotel" look like, and why would that be better for users than Google's?
plonk! ;-)
Absolutely great TV. Think Silicon Valley but with a name tied to it. We need to get the naming rights to get initial viewers, but you and me, DiabloD3, we have a show here.

Treatment:

Name: Ashley Madison or some generic name so as to avoid copyright and naming issues.

Dramatis Personae: Ashley Madison President, Ashley Madison programmers, IPO Finance Team, Hacker team

Story Arcs:

A Story: Follow the Ashley Madison president as he goes about his 2014-2015 tour to promote the site across the globe, focus on the Japanese campaign, in preparation for the IPO. Detail the trials and tribulations of the IPO setup, pressures from the M&A team. Then lead up to the hack and the bourbon scotch being thrown against a wall as a man who built an empire realizes it is crashing. The programmers in Ashley Madison trying to figure out if the data was expropriated, how much, and lead up to the internal discussions on the blackmail offer.

B Story: The hacker group recruits team members, identify weak points and sets up to acquire the data. Once the data has been lifted, they struggle on what to do with a release, expecting to have received blackmail monies, fending off the popularity it brings to them and how to exit what they have done.

The season ends when the news report starts to detail you can get the database on TOR.

This could be on HBO, Amazon, or Netflix.
Privacy Badger is awesome. ABP basically let's everything through
>> Does the processes read or propose the value ?

It does both, it first proposes by writing a sequential znode and then reads the children (all proposals are written under some parent znode). This is certainly assuming some experience with ZK, and I wonder if that's the problem. It was not the goal to go into a discussion of the ZooKeeper API, but I'm happy to clarify if this is what is preventing you from getting the point.

>> Not suppose to ? How do you ensure that ?

It is not supposed to in the sense that if this is implemented right, then the proposed values for each client won't change. The recipe guarantees it because it assumes that each client writes just once.

>> Sorry, but I fail to see what recipe you speak about.

I'm referring to these three steps: creating a sequential znode under a known parent, reading the children, picking the value in the znode with smallest sequence number.
The latter. The virtues of Elixir is that it is a functional language with immutable data structures, and that it does not support object oriented programming (which I consider a feature).
Someone needs to doxx these fuckers
The Easiest Way to Develop with Go – Introducing a Docker Based Go Tool
One point not mentioned in the OP: the people in charge of Firefox, Opera and Chrome have been and will continue to be a hindrance, not a help, on net to users who agree with the manifesto. The qualifier "on net" is intended to acknowledge that they do some pro-manifesto things, such as allowing any user to install any third-party extension, but that those things are cancelled out by anti-manifesto things, such as web fonts. (Note that these years, the company behind Opera gets most of their revenue from advertising.)

The people in charge of Safari, Edge and Internet Explorer have not been much of a help either although I suppose there is a chance that will change some day since their sponsors don't make most of their money from advertisers and other professional persuaders. (Although one could argue that the people in charge of Internet Explorer helped a lot in the 1990s and the first half of the last decade, I have seen no signs that they have been helping since then.)

Sometimes I think that the only way for users who agree with the manifesto to get free of the need for regularly writing new user CSS, installing new add-ons and extension and continuing to tweak about:config settings is for them to migrate to a browser whose maintainers have some sympathy for the manifesto.

I sometimes believe that what I just wrote would make a good business plan for a startup.

If I were to buy a phone or a tablet today, I would probably choose one from Apple just because of the content-blocking API Apple promised for iOS 9. (Yes, theoretically, the fact that much or most of Android is open source makes it possible for some new organization or project to offer an Android fork that offers even better ad-blocking than iOS 9 will allow, but after 23 years of experience with open-source software, I know that merely the existence of a particular software freedom does not mean that programmers and designers will do the hard work of converting that freedom into actual code that I will want to use.)
A much better solution than in Heinlein’s short story, "Gentlemen, Be Seated."
And just over there in the ocean is his ship, Loki.
It's not that there isn't a cause. But at some point, humans start dying of multiple systemic failures, and whatever proximate cause happens to lead to death, the root cause is aging.
An easy way to get out of the trap of having to intricately track your hours, and at the same time get paid more, is to bill by the day instead of the hour. All projects that you charge money for get a 1-day minimum. I've written a lot about this:

https://news.ycombinator.com/item?id=4101355

https://news.ycombinator.com/item?id=8706929

https://news.ycombinator.com/item?id=3420203

(and, like a hundred more).

I get a mail from a contractor about every other month telling me how much happier they are for having switched from hourly to daily. Daily should be your default.

(Advanced skill: daily->weekly).
You could replace Facebook, or Myspace, or Friendster, even.
Erlang/OTP is great fit for building applications that support a huge amount of concurrent users, but the problem is that IMO Erlang is nowhere near as pleasant to work with as Ruby, Python, etc. So if you're building something with zero users and choosing Erlang because of the ROFLscale potential it's premature optimisation. Elixir is the difference. I am just as productive in it as anything else and I enjoy it much more. So what we have is the massive power and potential of Erlang/OTP with a productive, pleasant API and great developer tools (Mix, Hex, etc).
It also reminds me a lot of agar.io
REACT.js – Multi Keypress Detection Handlers for React.js
The thing that always stops me from making something similar to this (other than willpower and interest) is: how do you enforce constraints on the data? How do you keep it from accumulating junk data if you're cutting out the role of an application validating it?

It could be that this is really only for directly-mapped CRUD data, but I haven't seen a lot of applications out there that don't require at least a little bit of integrity checking.
Yeah, we don't really (other than, perhaps, physical experiments as cookingrobot's reply suggests). I think such investigations are fun, but also presuppose a very misguided concept of the human and sociality.
Sure he's gone, but he'll have to pay $19 to have his corp email account deleted.
Maybe the editorial staff assumes the responsibility for all the correctness issues? That would actually makes sense, since they have the final say in what gets published and should do some additional verification. Just a theory. I don't read The Economist very often and never offline.
I think the social and cultural dynamic in most western countries means that women who want extramarital affairs have an easier time finding men than vice-versa.
> And if I had an idea for a better social network, I could replace Facebook.

Not necessarily. There are gigantic network effects propping Facebook up. A Facebook user who wants to try another social network needs to convince all their friends to move. And each of them has to convince their friends.

But to try another search engine takes takes about five seconds. You could switch from Google to Bing immediately and never look back, if you thought Bing were better.
> The question then becomes, if you manipulate your DNA, are you human, or a human subspecies?

That doesn't seem like a particularly interesting question. It wouldn't change the conclusion that humans can't naturally live past 120. And that conclusion itself becomes unimportant if we can reliably work around it.
Also want to mention that it's 100% free. No sign up, up-selling, lead gen etc...
How to Gain Respect from Your Thesis Supervisor Even When You Are Not Confident
I can already feel my brain slowly doing some kind of overfitting (in neural network terms), and that already bothers me without me being able to avoid it.

I can absolutely understand someone that says they would rather have a healthy <130 years life.