skysight-inc/HackerNews huggingface dataset:
The deaths caused by nuclear power aren't anywhere near the same order of magnitude as the deaths caused by coal:

http://www.theguardian.com/environment/2013/dec/12/china-coa...

>Emissions from coal plants in China were responsible for a quarter of a million premature deaths in 2011 and are damaging the health of hundreds of thousands of Chinese children, according to a new study.

http://www.theguardian.com/environment/2013/jun/12/european-...

>Air pollution from Europe's 300 largest coal power stations causes 22,300 premature deaths a year and costs companies and governments billions of pounds in disease treatment and lost working days, says a major study of the health impacts of burning coal to generate electricity.
OOP ideas aren't exclusive to that paradigm, turns out that things like polymorphism work very naturally in a functional language.
Is single sign on support for sub domains coming soon?
What's the Trick to Happy Startup Employees?
I am interested in references to these claims.
Found it, line 108 in lib/index.js

- phantom.create({ port: port }, function(instance) {
+ phantom.create({ port: port}, "--ssl-protocol=X", function(instance) {
Servers for Hackers – The Book
"Your web app runs on magic. Make it run on science!" @assertchris. Perfect newsletter. Book should be excellent too. Deserves support.
If I'm not mistaken, Nakamura was responsible for the white LED too -- Nichia Chemical made phosphors.
M Andreessen on Apple Watch, Zuckerberg, Twitter, Bitcoin and Dot-com Blunders
Microsoft creates room-based gaming technology
I've used it even for fairly small amounts of user data (a few gigs max). What we had, though, was a load balancer out front that would ensure only one node was ever receiving writes (lazily switching on failure), and were relying on it solely for fault tolerance (which, despite the article, Mnesia can do just fine at, with certain caveats; what it can't do is scale).

In the event of a network partition, the load balancer is channeling all writes to a single node, and the system rather loudly lets us know that a node disappeared (in the event of a network partition, every node is loudly letting us know that a/some node(s) disappeared), ensuring quick redress. While it's possible that in such an event the node being written to will go down, causing the load balancer to switch to the partitioned node(s) (thereby creating an inconsistency), this is generally over a -very- small time window, as the facility this was deployed into is manned 24 hours. Thus, any inconsistency is confined to a very small window, approximately half of the time between the initial split, and its being addressed (as if the failure that causes the load balancer to switch to the other node happens before then, we could take the switched to node as most canonical, and if it switches after that, we could take the switched from node as most canonical), so even without an express mechanism to resolve consistencies, we're losing very little data, and for such a rare occurrence (multiple years running in multiple locations and we've yet to see it happen), that's an acceptable risk.

It just depends on what your requirements are. The author is bang on that Mnesia should not be used for scaling (and in general probably shouldn't be used any time you don't want a full replication on every node, or relying on some other mechanism to reconstruct/deconflict data), but in an environment where split brains are infrequent, where you've got Nagios or similar running to alert you to a split brain, and you've got people on call, where scalability is not a concern, and where in the (extremely) unlikely event you actually lose some data it's okay or easily addressed, Mnesia can be a reasonable solution, since it's so easy to get running with, and quite performant.
6 Productivity Tools That Helped Grow Our Business
I'm surprised recognizing an animal in a photo is his example. Apparently computers are already almost as accurate as people. https://karpathy.github.io/2014/09/02/what-i-learned-from-co...
Might be interesting to compare to
https://news.ycombinator.com/item?id=8411225
I don't see how it's a loss of orthogonality; just like a whitespace-insensitive language, it's saying that the choices of bracket and dot are syntactically equivalent. And that syntactic freedom means the precedence of a Scala line is often much clearer than the equivalent in other languages:

a b {c d (e f g.h(i))}

In Haskell you'd have to write that as something like:

a b (c d (e f (g h i)))
//or alternatively
a b $ c d $ e f $ g h $ i
I failed a travel planning start-up in 2007. Way before our time, I guess.
Building a light fixture for slide film
Perhaps the issue is that the slides don't really stand on their own. Without hearing what you have to say for many of the slides it is difficult to really get the point you're making. Let me just address the "bad" slides, and what I got from them.

Slide 8

- Compiler too slow. A common complaint. Agreed it could be faster.

- Ecosystem. Don't really get the point here. Yes, Scala has different idioms to Java, so naturally Java libraries don't make for idiomatic Scala code. There are many mature Scala libraries. Binary incompatibility has not been a problem for me in at least two years, and it is a necessary artifact of Scala compiling a language that is not Java to JVM bytecode.

- Lambdas I addressed above.

Slide 9

Don't know what point you're making here.

Slide 10

Mostly addressed above. Syntax doesn't bother me. There are regular rules and the alternatives are a consequence of those regular rules. Would consider removing eta-expansion. Never had an issue with any of the rules though.

Slide 11

See above.

Slide 12

See above on type classes.

Slide 13

This is very generic. Applies to all languages.

Slide 14-15

Don't really get it. You can write code in many different ways. Applies to all languages.

Slide 16

This is very generic. Applies to all languages.

Slide 17

Don't get the point you're trying to make with this code.

Slide 18

This is presumably a slide that summarises this section. Without hearing what you have to say here I can't really interpret this.
There are already two such tiers: Pro and amateur.
I agree although Adobe refers to this behaviour as 'responsive'. They probably shouldn't :)

This is project mainly designed with a tablet in mind as it can be used with touch swipes on both the dial and the panels. I thought it was an interesting UI approach.
Great article. Thanks for being so rigorous with the step-by-step process and for annotating your thoughts on each step, it's very instructive.
Yeah. It means you can e.g.

respondWithHeader(`Content-Encoding`(UTF8)) { ... }

and the header and its parameters are typed, and so if you make a typo in the name or the value (or try to pass the value of one header to another) then you'll get a compile-time error.
Gutta cavat lapidem (Ovidium)
Occasionally someone asks you to reply. Generally "click here to ack receipt of this mail" but sometimes "please reply to this mail to confirm that the email address works".
> "First, TLS doesn't just guarantee confidentiality, it also provides authentication and guarantees the integrity of this page. That prevents an attacker on the network from serving you bogus content, and pretending like it's from me."

But it doesn't though. If (for example) you're using Cloudflare's free SSL then the SSL termination is at their servers and theres nothing stopping the them from mangling the page between the original server and them passing it on to you.

How do you actually know if you're connecting to the server and not some terminating load balancer and the connection is unencrypted from there to the server?
How AT&T could have avoided their Security Breach due to an employee
Learn to de-provision correctly.
Companies use a variety of software applications on and off the cloud to ensure that their day-to-day work gets done. Each employee has their own individual account on each of the applications. But let’s say that you have to de-provision an employee that has left the company. Your administrator has written a document that describes the procedure for de-provisioning an employee from each app. It will remind him to de-provision an employee from Microsoft Exchange, Google Apps, SharePoint, Dropbox, and any other application that employee uses in his daily activities.

Oh! What’s this? The administrator forgot to include a reminder to delete the employee’s Podio account?
Let’s say that you have lost 400 employees in the last year. That means that there are 400 Podio accounts — some of them belonging to ex managers — floating around. If, at some point, one of those accounts is compromised (and this kind of thing happens all the time), then this gives the hacker free reign on your entire CRM system.
Before you de-provision someone on PerfectCloud, you have a list right in front of you of all the applications that this person uses. Provisioning and de-provisioning is more of a breeze and less of a hair-curling nightmare that people tell stories about around a campfire. By using this system, you ensure that you don’t leave behind any zombies. Besides, it’s also a cost-saving opportunity since you don’t have to pay for accounts that are inactive and forgotten.
Announcing NetBSD 6.1.5
Depends on the language. Clearly 'lpDataPointer' suggests C or C++, but if it was C# or Java then 'return p;' would only compile if 'p' was of boolean type.

</pedant>
It all happened before and it will happen again.

http://en.wikipedia.org/wiki/Boxer_Rebellion
Here's a guy who's done a pretty cool project with Node-RED, an Arduino, a Raspberry PI and Minecraft: http://blogg.bouvet.no/2014/08/04/node-red-how-it-simplifed-...
Kid, how have you grown? The amazing progress of computer vision in recent years
A little question: what is the name of the color scheme using in this article?
Programming is like learning music.

Some people are willing to invest the time needed to learn to play piano, guitar, violin...

Others are happy to be able to play triangles.
Is Cruise Automation still on track for 2015?
Fortune-Tellers, Step Aside: Big Data Looks for Future Entrepreneurs
Would be interesting to see a model to come up with such numbers. And it would as well be interesting how in such a model the nuclear waste is taken into account, especially the one that risks to pollute some day in the future. Such models might give us an idea of how many more nuclear catastrophes humanity can "afford".

After Fukushima happened, I heard or read several times (without being able to quote, probably radio/TV) predictions that big nuclear accidents like Tshernobyl and Fukushima will get more frequent in the future, because (a) the reactors get older and (b) more reactors have been built in the mean time.

I hope that future will prove these predictions wrong, but somehow I feel that hoping is not enough. And incidents like these where security limits are relaxed [0], don't really reassure.

[0]: Quote from the article:

"EDF was granted permission by the regulator in the summer to relax its graphite weight-loss limit at the Dungeness reactor in Kent from 6.2% to 8% after it came close to breaching the original safety margin."
It would be helpful if you explained the relevance of the distinctions you are making rather than simply their existence. Not to mention the relevance of this entire derailing of the underlying conversation.

The delete button works just as well for "I hate your core identity" as "I'm looking for a javascript spetznatz".
It's a high-trust environment, and I think very few judges would demand an official transcript. What's interesting is the risk-versus reward here. You can get disbarred many years into a successful career if this came to light. Meanwhile, clerking for a judge is mostly resume polishing. It's very educational, but you end up working the same job after your one year appointment, you just get to signal to your lawyer friends you had really good grades in school. To Martoma, that was apparently worth risking his career for an indefinite period into the future.
Fully agree, the future is multi-paradigm.
You can download the episode, without subscribing, from the EconTalk "page", or whatever it's called, in the iTunes store.
Viewable with Any Browser: Campaign (2011)
I'm not sure I understand the tradeoff. Given two tasks requiring an equal amount of work, are you saying that it's better to spend it on a 5% improvement than a 150% improvement? Sure, if all you have available are lots of 5% improvements, they'll also eventually add up. But won't you prefer to work on the biggest improvement/cost tasks first?

Perhaps it should be seen versus the "throw it all away and start over" tendency? Like in steady refactors vs. big rewrites.
Nice work!

Can you please provide an example for using `evaluate()` to get the page's content?

I tried this, but didn't get anything:

new Nightmare()
.goto('http://yahoo.com')
.evaluate(function (page) { return this.content; }, function (res) {console.log(res);})
.run();
No single country has yet found a safe, clean and cost-effective solution for coal waste disposal either.

If you are going to get into the externalities of nuclear power, then you have to do the same for other technologies.
No, you're not correct. You are conflating a number of different things (e.g. fractional reserve banking, interbank lending, capital adequacy requirements) to come up with a deeply flawed understanding of how banks are regulated.
A lot of modules are pure Lua. They may depend on a few critical C libraries though. But with just LuaSocket, LuaFileSystem and maybe LPEG you can use most modules.

There are several ways to build those critical Lua modules statically, one being https://github.com/stevedonovan/luabuild Even without those, it is not very hard to modify the makefiles to build statically.

About the bloat: this is certainly true for some modules and not others. As I said in the talk, everybody uses Lua differently and nobody will use all the modules and tools available, but there is still some amount of code that can be shared.

I mean: you could say exactly the same thing about C, and it still has a lot of libraries.
You still have to put code inside an object, but it's two lines of boilerplate rather than Java's 8 or so:

object MyApp extends App {
code here
}

I tend to use Maven to build my projects, so test classes have to go in src/main/test, have names ending in Test, and have their test methods annotated with @Test. But there's nothing to stop you making another App that just runs tests when it's executed, if you want to do that.

Things should be orthogonal, and that's usually something Scala is very good at, e.g. the way (scalaz) Futures are handled is IMO a very elegant balance between exposing the difference between sync and async code and not making it too cumbersome to use.
As someone who doesn't know anything about DNSSEC, that was a helpful introduction!

One thing I don't understand is, why all the complexity in NSEC/NSEC3? Couldn't you just have an NSEC-type record that returns "tustee.ietf.org does not exist" for a single record rather than a range?

If the issue is that returning any result for tustee.ietf.org would be construed as a positive "it exists" by older resolvers, couldn't you just namespace it behind not-found.arpa or something?
> Mythical Man-Month

Critically flawed and wrong? Doesn't the main insight of this book -- that adding manpower to a late project only makes it later -- ring as true as ever? Fred Brooks isn't a phoney like Gladwell, either.
How credible is the source? I Dont see this news anywhere else.
I agree many parts can be brought to FP but most importantly the languages of the future must be developed with tools in mind and in tandem with the tools. Too often new langs seem to be developed as command line compiled experiments which only (much) later get IDE support. At that point some decision may already have been made that makes tooling harder, such as not allowing or encouraging methods "on" types.
I've used Scala on and off professionally for about 4-5 months and the best advice I could ever give to someone using it for the first time is to try and treat it like Ruby but with type safety.

As numerous people before me have said, the language is a mess. Although it offers some benefits, the syntax is so absolutely bloated that you're probably better off taking the time to really consider whether or not you absolutely need it for all of the headaches and unreadability you're going to run into in terms of code. There aren't many Scala developers out there and the learning curve can and likely will punish you when things need to get done, assuming you're bringing in new developers.

The open source libraries all generally seem to have glacially slow development processes, which in some cases might be considered acceptable, but when the main Scala team pushes out 2.11.x (and to some degree actively encourages its use) and X framework you're using literally cannot run because library Y is not compiled against it, you end up stuck on Scala 2.9/2.10 which is really unpleasant for you because you're missing out on the speed increases and other quality of life improvements (how many times have you run into the 22 argument limit for case classes on 2.10?).

Perhaps I'm asking for too much, but Scala strikes me as a language that's supposed to be moving a bit faster than Java in terms of development, but that doesn't really seem to be the case. All in all, while it has some neat parts, if I never got to work with it again I wouldn't be crying about it.
Abu Ghraib.

An 'authority' doesn't need to be a person. It can be a culture. The point of the experiment is not the literal situation or situations resembling it: it is how easily otherwise non-cruel humans can be persuaded to engage in cruelty. It's the hundreds of variations of the experiment that you could employ to get your underlings to behave in this way that is the lesson that bears repeating again and again.
For those that are interested, there is an interesting article here [1] about how people beat drug tests. It talks mostly about crossfit but applies to a lot of sports.

[1] http://www.t-nation.com/steroids/beating-the-crossfit-drug-t...
I'm interested to hear the critiques of Synrock as one method of addressing this problem.

http://en.wikipedia.org/wiki/Synroc
Sierra Nevada Corp Challenges Award of NASA's CCtCap to Boeing and SpaceX
True, but as SQLite is heavily used in mobile applications it still has the advantage of consumes less CPU and thus less battery.
Is this legit? None of the larger media outlets are not reporting this yet.
I don't know enough about the others to make too much of a sweeping statement on them, but the heart of Mythical Man-Month is absolutely true and valid. It just has a bad title, so people assume it means something it doesn't.

The heart of the story is this: Adding developers to a delayed project will only delay it further. It's not about parallel vs serial. It's about project management and how to handle delayed projects. I have yet to meet a PM in my career who really understands this, and almost all of them have referenced the saying, "Nine women can't have a baby in a month."

To claim that it's "crap," "critically flawed," and "wrong" strikes me as naive, overly general, and dismissive because you can throw it into a "Gladwellian" bucket and be done with it. Fred Brooks learned his lessons from years of project management. This wasn't a guy who conjured up an idea for a book or a TED talk and just slapped some crap together.
typo
*None of the larger media outlets are reporting this yet.
In plain text is bad enough: bad would this have been found without it?
disk io is often the bottleneck in the database area.

SQLite usually gets used in situations where the data easily fits into memory (multiple times). It isn't really postgres ;)
Which I believe is in fact the case for many of these improvements as per discussion on the thread.
Ask HN: Sweat Equity Agreements – What Works and What Doesn't
For those of you that have been part of (as founders, employees or investors) a start-up that had sweat equity agreements, what aspects of the agreement did you feel worked and what did not?

I'm a full-time sole founder of an early stage startup. I want to bring aboard one or two partners who will work on it part-time until cash flow is sufficient to offer a salary. A lot of advice out there talks about providing sweat equity, but sweat equity agreements seem difficult to do well.
How to publish content on GOV.UK
https://roadtrippers.com/
1% / 8 = 0.125%
It was the glgui library that gave me that impression. It's true that there appears to be no built-in high level concept of a view as a container/ layout holder/ etc, we are talking about different things. I should rephrase that as "kind of GUI as long as you don't want to dive into raw OpenGL". It was more like, if I want to change how a button is drawn, do I have change the internals of the framework or is that a user-level supported API?
Haxor Lands in Hollywood
Marc Andreessen on Finance: ‘We Can Reinvent the Entire Thing’
In india the phrase is:
"Continuous movement of rope can make mark on stone, like it makes on the wall of a well".

HINDI: "Rasari aavat javat re, sil par parat nishaan"
The #1 Metric for Startup Fundraising (hint: awesome)
You might find this take on the question interesting:

http://pubs.acs.org/doi/ipdf/10.1021/es3051197

He shows that since the invention of nuclear power, it has saved 1.8 million lives relative to the obvious alternatives. Since its invention, nuclear power has killed about 5000 people. That makes it about 360x safer than deployed alternatives and yet, somehow nuclear is the technology that must justify itself on safety grounds.
We moved our company 795 miles and nobody noticed
...on any browser?

I just explained (somewhat jokingly) how to open a New Incognito Window.

When you do that, you won't be logged in when you search.
I don't doubt they're mostly telling the truth about themselves, but beyond that? It's more difficult to say.

> And I'm not really convinced that, in cycling, for example, it's realistic to have cyclists run through hundreds of kilometers of mountains day after day and still being as fresh as ever. But hey, believe what you want.

Ah, "it's tough, so it can't be true!". Those guys are the best at the world at what they do, and the ones they show on TV, are of course in the lead, so by default the ones in good shape. If you go see a bicycle race in person, you also get to see the ones lagging behind, some of whom are suffering a great deal. Truth be told, so are the ones in the lead, they're just going faster.

It's really hard to know exactly what's going on, but my whole point is that there are at least a few guys who compete clean. Saying they are all doping is extremely demeaning to those who do compete clean.
I'm glad to see something like this. People often take the typical optimization mantra too far. The minute you mention optimization on most internet forums (especially StackOverflow) you get slammed for promoting "premature optimization."

That's not to say premature optimization doesn't exist. Sometimes writing faster code is the difference between using a hash instead of a list. Sometimes it's spending an entire day optimizing a function that's called once. The former is performance aware, the later is premature. It seems as though most would have you believe that they both fall into the "premature" bucket.

It's as though people are using it as an excuse for their personal ignorance and would rather continue to revel in this ignorance than expand what they know. As far as I am concerned these "unimportant tidbits" about performance are gifts that keep giving.

/somewhat offtopic rant
Haha nice irony there. It's indeed a fundamental principal in science. Not really sure why the author is complaining about that!