skysight-inc/HackerNews huggingface dataset:
>C# is a great language to work in when making backend services for websites, IMO (even though there's a whole load of crap that comes along with the framework).

Exactly how I feel. I've been working professionally with C# professionally for over a year now doing a lot of backend stuff for websites and it's great. .NET shares a similar philosophy with Python in that it's a "batteries-included" language. Need a REST endpoint? I can have one up and running from scratch in under 5 minutes with WebApi. Inter-process communication? Let me create an MSMQ instance - done! The only downside is what you mentioned - whole loads of crap that come with the framework. I hate IIS for this reason (but love how easy it is to deploy web services). We're currently working on an HTML5 replacement for our current Silverlight stack (lol) and wanted to go with Node.js instead of IIS, but we really want C# on the backend and don't want to hack it. From our point of view, JavaScript is great for the front end but completely idiotic for the amount of work we do on the backend. Type safety and static compilation is essential for us.
Would love to use this for on-demand IPython parallel computing.
That photo is next to the parking lot where he "found an empty lot where [he] could safely continue the experiment" and then "they cut the Jeep’s brakes, leaving [him] frantically pumping the pedal as the 2-ton SUV slid uncontrollably into a ditch"

Not the highway.
In addition to your third paragraph, auto makers are disincentivized toward adding security features because they CAN'T advertise them. If Toyota started advertising the all new Prius with the feature "your ability to brake won't be taken away from you while you're barrelling down the highway at 70 mph", consumers wouldn't just not care, they would question why the fuck that wasn't there in the first place. This sort of stuff is expected to have been there from the start by consumers, so at this point its nothing but a cost sink to add it.
"stay strong"

People typically use the phrase when they really don't know what else to say. For the most part, its not to be mean or just tell you to be normal, its they don't know the words to say since they have never had to deal with a clinically depressed person is going through. You can rage at them, but it won't help either person.

We don't deal well with mental health in the US. There is a political legacy from both parties and their interactions, and when an event comes along that is clearly a mental health issue we blame some inconsequential symbol to fight as opposed to doing the hard work. I get the feeling living in a hashtag-protest world is not going to improve the situation for mental health issues.
That looks like a staged shot. Highways don't have corners like that.
> We're capitalists here, mostly, so people don't mind.

I have never thought [citation required] was more necessary than with this comment.

We're technology professionals or enthusiasts primarily here.
What on earth do you think you are going to accomplish that will have any positive effect whatsoever by calling the cops of all people?
Michael Hastings. Look into it.
I like this a lot. It's similar to lljs [1] in allowing small amounts of asm.js to be generated, using a familiar syntax (C). That's an important use case and indeed Emscripten doesn't really support it.

Two comments on this bit:

> Wait, what's wrong with Emscripten? [..] It's perfect if you've got a great big POSIX C + SDL codebase that you want to run in its own self-contained environment in a browser, but it's not very helpful for writing idiomatic Javascript code that just needs to drop into optimised asm.js occasionally for some heavy lifting.

First, I think this correctly describes some important use cases. But more generally, I think the main use cases I see in this space are

1. Complete C or C++ programs, like a 3D game engine. Emscripten mainly focuses on this.

2. A C or C++ library that people want to use from JS, like Box2D or Bullet. Emscripten focuses on this quite a bit as well. You can disable filesystem support and other unnecessary features for such pure computational code, and then for a library the size of Box2D or Bullet, Emscripten's runtime isn't a significant code size issue. And it provides tools to make C++ objects look like JS objects, so using such libraries is convenient (see ammo.js and box2d.js for examples).

3. Small amounts of C that are to be "embedded" in JS. lljs and Bonsai-c focus on this.

A second comment: The third use case here is easy to get wrong. There is often a cost to calling from JS to asm.js and back. Writing a little asm.js function that adds two numbers and calling that in a loop will generally not be efficient, both because such functions are often optimized to asm.js-like speed anyhow, and because of the JS<->asm.js overhead. To make it worth it, the asm.js needs to do a more serious amount of work. Just mentioning this because it seems like a common pitfall.

[1] http://lljs.org/
> it's also legal for her employer to be upset that she's making the work environment more difficult for others

I guess I'm not done, because I am compelled to point out that this is completely false. That's the entire point of all of the legality around the protection of these discussions under United States law: that, no, your employer cannot be "upset" at you for choosing to exercise that right.
Yeah absolutely I'm critical of suburbia as I see it currently implemented.

There's nothing wrong with the concept of living outside of the city, but the problem is the design and form of development that many suburban cities have taken.
It's refreshing to see a company getting acquired and instead of shutting down they double down on their product/service.

Congratulations to the Pixate team!
I mean, the going stigma out there is, sorry Cuban, "You have to work 24/7/365, because business is a sport and there is always someone looking to kick your ass".

The problem with this is we are human. We get stressed, we get depressed, we get overly confidant and then utterly destroyed when something does not work out that you've put everything into.

The stigma of having to work 24/7/365 is just a saying. Balance of work, exercise, social interaction, relaxation, and sleep is far more important. Yes Mark Cuban said that, but what does he really do? Even when hustling very hard, he still went out to the bars with friends, still relaxed, etc. What he really meant is that when he WAS working, he was working incredibly hard.

What I'm getting at is the quotes and the movies/shows of programmers pulling 24 hours straight is not healthy. Yes it has been done, even by very successful people...Bill Gates, but how many do you not hear about? The ones who take their own lives or become depressed for very long periods of time.

Working like this is dangerous. Balance is key, we are only human.
I'm not an expert on either of those, but I don't think that your ERB version does the same thing. If delta is not set, the react version renders something like

<div class="card">
title
</div>

If it is set, it renders something like

<div class="card">
<strong class="text-success"> delta </strong>
title
</div>

Your version appears to render

<div class="card">
<strong class="text-success">
title
</strong>
</div>
This is so important that it is worth repeating.

> Stallman created the GPL because he cared about user freedom.

> Stallman created the GPL because he cared about user freedom.

As GPL has evolved, the focus on user freedom has gotten clearer. It is not that GPL is against freedom for developers or software vendors. However, the way I understand it the consequences in this area are more side effects than guiding principles.

It is not like the focus suddenly changed at some point. It has alwasy been this way. Let us look at how FSF defines free software:

> A program is free software if the program's users have the four essential freedoms:

> The freedom to run the program as you wish, for any purpose (freedom 0).
> The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
> The freedom to redistribute copies so you can help your neighbor (freedom 2).
> The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.

Without even reading the four points, we already see that what defines a software as free software is whether or not the "program's users" have certain freedoms.
https://www.gnu.org/philosophy/free-sw.en.html

(I am not a lawyer. This is just my personal interpretation.)
Those are not really side-effects of Naloxone, they are side-effects of reversing the effect of opiates. So if an addict were to quit an opiate addiction cold turkey, they would experience some (or very rarely, all) of the effects you listed. If you give Naloxone to someone without opiates in their system, they wouldn't experience those effects. What Naloxone does is kick opiates off of opiate receptors in the body, which instantly puts the addict into a state of opiate withdrawal.
I really don't see the relevance of this blog post. What's so important about this story to be shared here?
I wonder if a court would see it that way, rather than a simple exchange of considerations, in which the employee failed to hold up his end of the deal?

Maybe this employer didn't have an employment lawyer draft or review the contract for them, and the law holds that the employee can treat it as an "interest free, unsecured loan with no minimum payment and no unspecified term." Or maybe they don't really care about $35K or whether the employees they give signing bonuses uphold their end of the agreement.

It's possible, but I have my doubts.
Calling the police on security researchers...I honestly cannot believe this is considered acceptable behavior.

Who cares what their job title is? They deliberately blocked visibility and then cut the transmission of a vehicle being driven on a public road in traffic. That is well into the territory of criminal negligence.
Picture of Original Penn Station
"Stallman created the GPL because he cared about user freedom."

vs.

"The GPL attempts to force people and businesses to release their source code. There is nothing wrong with that, except I don't think it qualifies as "free software". I want anybody to be able to do anything they want with my programs and/or its source code."[1]

And I agree pretty much with the latter.

1. http://www.linuxjournal.com/article/5935
Chromium certainly didn't usurp anything. Chrome, the proprietary browser, did.

As for Firefox, the Mozilla Public License is actually a (weak) copyleft license, since if you modify any file, you must distribute your changes - it's closer to the LGPL than to MIT/BSD. And the other licenses under which Firefox is distributed (it's tri-licensed) are GPL and LGPL.
Been watching this story rise since the beginning. No comments left, nobody pays attention, even the title is out of place (what is joinong a repo anyway??). I think there's some magic behind the points this is getting on HN. :-)
This was phrased really well in the movie/article, worth looking up:

> “I instantly realized that everything in my life that I'd thought was unfixable was totally fixable — except for having just jumped."
Here's why I (and jawngee) never used Pixate's products for my apps: https://news.ycombinator.com/item?id=5062868

Given that I only make iOS apps, and that Google acquired them, I feel vindicated 916 days later.
was about to write a response, but bkeroack did a perfect job with the above :)

Full disclosure: I work at Google on Kubernetes
I think the point is that you, and the researchers, have no right to make that decision for other people. It's illegal to purposefully stop in the middle of the highway. It's illegal to cause someone else to do so as well.

People who routinely test things that have the capability for real harm learn to take precautions for as many of the the things you don't think off as you can. For example, the Mythbusters are routinely testing things with cars and other bits of machinery that can cause physical harm if something goes wrong. They also routinely retire to abandoned airforce bases, remote locations, and the salt flats to test things.
I'm involved in Neonto, a startup that makes a design tool that targets both iOS and Android:

http://neonto.com

The unique twist is that Neonto Studio generates real native code (Obj-C for iOS, Java for Android), so it's possible to use it even for complete apps, not just prototypes.
There is a difference between "therapy" and "counselling". It's a shame that the difference isn't clear enough.
If a company decides that exercising one's rights is "troublemaking", that company should be utterly destroyed without hesitation or remorse.

The corporation exists solely at the sufferance of the society that grants it its charter. Someday maybe we'll remember this instead of throwing our hands up in the air and giving up.
Pixate has a middle term potential to fix the difficulties with designing and deploying UI's which require basic physics or animations. It has the long term potential to change native front end engineering as its currently done.

Potentially it could compress design, prototyping, and front-end dev into a single seat -- who is more design-forward rather than coding-forward.
I definitely don't want this to come off as a sales pitch, but you can get started in one click using Google Container Engine (and $300 in free credit) as well.

Full disclosure: I work at Google on Kubernetes
It's great that you're sharing a very practical tutorial, but did it occur to you that women (and generally reasonable people) might not be particularly motivated to learn how to build a woman judging app? Seems like your example project could be less alienating.
There's far, far more than Plan 9. That's only the beginning. Many others iterated heavily on Unix architectures to make them more novel, or started from scratch. John Ousterhout and U.C. Berkeley developed Sprite, which introduced things like checkpointing, live migration, SSI, log-structured file systems and other things. Andy Tanenbaum did Amoeba, which is sadly only remembered for being the platform that birthed Python. Spring was Sun Microsystems' research system, the name service of which brilliantly resolved the problem of "naming things" (I highly recommend you read this paper: https://www.usenix.org/legacy/publications/library/proceedin...). Unfortunately, Sun barely implemented any of its ideas to Solaris. Just the least interesting ones like the doors IPC mechanism.

Never had wifi.

Well, it was developed during a different time. It did get wi-fi thanks to 9front, though.

linux seccomp-bpf

A sandboxing/syscall filtering mechanism. Nothing new there, and its interface is rather leaky, much like Berkeley sockets are.

freebsd capsicum

This is one of the few legitimately interesting projects going on. Bringing capability-based security on top of fds. I don't know if it'll catch on beyond FreeBSD, though. Google seems to be an early adopter.

containerization

Nothing that IBM didn't do much better. Docker reeks of opportunism.

sendfile(), epoll() / kqueue()

sendfile(2) is just a cheap trick that got turned into a syscall: https://groups.google.com/forum/#!msg/golang-nuts/gdp1q6T0DN...

epoll(2) isn't anything special, it's a rather convoluted if performant I/O multiplexing mechanism. kqueue(2) is much cleaner designed, at least.
man I was thinking about this the other day. Love that windows has this built in, while all OS X get its a shake-to-maximize cursor that you can't turn off. :(
That is a very specific case.

But since you bring up the iphone. You know that the iphone is fundamentally based open permissive licensed software? I can't think of a more user freedom hostile platform than the iphone...
Right, and/or a way to test something just to see it in action for <1hr or so.
Apple Music, App Store, Beats1, iTunes Experiencing Outage
They might be reasonable in isolation but are not being levied remotely in proportion.

I just realized what the problem is: this is bikeshedding. Everyone knows about people driving around and feels qualified to have moral indignation in that area, whereas few people know anything about actual cars.
The funny thing is, that I actually never mentioned privacy concerns here, my "anon" name comes from funny times on 4chan several years ago.

I just don't want to build anything of value ontop of their products, either because work customer contracts demand privacy policies, or work today must be maintained the next 20years to come (non-startup environment) and my experience with google is that they don't care about these scenarios.
Looks pretty cool! I like the graphics. I think Meteor.js does this too, but with only one resume buzzword.
I would disagree with that statement. Nuget packages make it incredibly easy to use other people's code in C#. You add the package, and it's ready to be referenced. Automatically pulls it in on builds, too.
Kubernetes does this as well:

cluster/kubectl.sh exec pod_name -ti bash

Full disclosure: I work at Google on Kubernetes
iSperm Automatically Analyzes Sperm Concentration and Motility Using iPad Mini
Digital transformation challenges the age of mobility,cloud computing,& big data
The users you disparage are mostly good people who just aren't obsessed with technology, or its implications on privacy, as we are. They just don't know any better than to do what they do on LinkedIn and Facebook. I daresay you need to get out more; then you'll see these users as real people, and not one-dimensional subhuman things to be monetized.
It is just as unrealistic as the blurring that happens in Cascading shadow maps but it is more efficient.
I'll caution that the situation that we came out of in the 1950s and today are very different. There are many things that are driving the congestion of the roadways in the US. One is, for sure, the move to more urban environments. Why that is depends on a multitude of factors. I'll caution that we have significantly more people in the US than we did when the Levitt-towns were being made. In `950, ~150 million americans were alive, today there are ~320 million, a 110% increase [0]. I'll also say that anecdotally, people are congregating in urban areas because there is more flexibility and agility there. You used to be able to live in a small rural town and work there just fine. Now, if that steel mill or logging operation goes out, you have to move very far. In a city, you can find another job somewhere, and possible through referrals.

[0]http://www.demographia.com/db-uspop1900.htm
Look at what Toyota did with the whole unintentional acceleration thing. About as irresponsible as you can get.
Oh boo hoo, get a better job with less shitty restrictions, you weren't forced to take those positions or sign those contracts.
A few years from now, when you want to hack on some new gizmo and you find out that the toolchain is a pile of proprietary blobs that only work on Windows and an old version of RHEL, you can thank the "pro-user" supporters of clang and its non-copyleft license.

(I think this is already happening with GPU toolchains but that's not my field.)
JPAUnit – A library to assist with testing your JPA code
A bank can use a copyleft encryption library without open sourcing their entire banking system. You just can't make changes to the encryption library without releasing those changes.

The Linux kernel is GPL and is used in countless proprietary applications.
Data Science and Disney Movies
Things like http://yeoman.io/ likely have something to do with it.
Around the World with Uber
We should not jump to conclusion and say this has anything to do with her startup.

The most important sentence here is sprinted toward a shrubbery-lined.

Someone who rushes (as in running) to their death is not similar to someone who walks and jumps.
How does this get zero comments? Bummer. Would've been a great discussion.
It is psychological, for some of us freedom means I authored this piece of code and if you want to use it you do what I say aka GPL.

For some other people it means that here, I wrote it and you use it as you want to use it aka BSDL.

I am more likely to side with BSDL guys on this one, I do not want to do anything other than use a free software as free software if it is branded as free software. :)
Networking on AWS works fine with no additional networking as well.

Overlay networking is not required if you're running within a bunch of nodes that can see each other. Only if you get more complex will you require something, and there are quite a few solutions (Flannel, Weave, Calico, etc)

Full disclosure: I work at Google on Kubernetes
I'm not familiar with "douchebag" being used to mean wealthy.
Interesting idea. Do you have any Docker configs currently for that?
There was a YC proposal by a couple of cofounders who wanted to start a business around this premise and had a working prototype, including WEB IDE integration for quick PR submissions.

I met with them about a year ago, thanks for reminding me to check in!
I feel like a lot of the comments in this thread are conflating permissively licensed software with closed source software.

If you want to write software and keep it closed so you can make money off it I don't necessarily love the idea but I can respect it.

But we're not talking about closed source here, just the difference between the GPL and permissive licenses like BSD, MIT, etc. I don't see how creating a killer app and releasing it permissively guarantees a developer an income. The opposite is the obvious effect. On the other hand using the GPL as your public license and negotiating a private license with a company like QT does seems like a logical way to provide user freedom, enjoy feedback and improvements from the community and still allow for a revenue stream.

It's definitely a tired argument at this point so I was actually pretty happy when the author went out of his way to reiterate at the end of the article that there are benefits to both approaches, why can't we all just get along...
And a hammer is perhaps as old as humanity.
Your ERB function is actually wrong though....

<div class='card'>
<% if this_props_delta? %>
<%= content_tag_for(:strong, :class => @delta > 0 ? 'text-success' : 'text-danger' ) do %>
<%= @this_props_delta %>
<% end %>
<% end %>
<%= @this_props_title %>
</div>

I'm not a rails developer, so I'm only marginally certain of the correctness of this, and less certain if there's a more verbose way to write it. Likewise, I've only played around with React, so its possible that the React version can be made less verbose.

One could just as easily argue:

<div className='card'>
{() => { this.props.delta ? (
<strong className={this.props.delta > 0 ? 'text-success' : 'text-danger'}>
{this.props.delta}
</strong>
) : null }() }
{this.props.title}
</div>

Is the same amount of typing. Honestly though, I feel as though this whole argument is a bit of an apples-to-oranges type of argument.
Whenever I'm hauling >10K lbs with my pickup truck, I get most nervous going downhill through mountains. The only thing between me and hitting something are a thin set of brake pads on all four disc brakes and the extremely limited compression braking on a ~6L engine.
if they wanted to make microbiome data available they could just share some
The test automation basics every software developer should know
No, there's a private network that's shared between all the containers running on the pods, but as long as the nodes can see each other, you're good.

Full disclosure: I work at Google on Kubernetes