skysight-inc/HackerNews huggingface dataset:
Brings up the broader question of "are people with criminal records simply unhireable?"

Give people a second chance, a few of them screw up, and it's your fault for hiring anyone with a record. Don't give anyone a second chance, and having a criminal record becomes a ticket to lifelong unemployment.
Off topic. GoatAttack is the coolest service of all time.
React CountUp
The problem is that it doesn't often come down to what will have profound social impacts, instead it tends to be what the loudest group of folks disagree with.

Those are two different things.
The more I learn about HyperCard, the more amazed I am about how nifty piece of technology it was. Too bad I haven't been fortunate enough to ever use it.

http://www.jaedworks.com/hypercard/HT-Masters/visual-effects...
Exact same feeling here, well put. I recently started Tyler McGinnis' excellent React.js Fundamentals and the entire first section of the course is setting up Webpack, Babel, etc. Once you're set up there, then you need to decide how you'll handle routing, AJAX - and so on.

The older I get the more I hate third party dependencies. You're asking for trouble.
>GitHub should look into this, otherwise we get git repos with directories that are thousands in length.

In a way, Github already looked into it extensively while helping resolve the issue where CocoaPods monopolized their servers and hit CPU rate-limiting. Whether it's abusive or not was already debated ad nauseum when it happened, but either way they came to a set of solutions which might help anyone else wanting to use Github for package management:

http://blog.cocoapods.org/Master-Spec-Repo-Rate-Limiting-Pos...
Checkout React CountUp at https://glennreyes.github.io/react-countup/ . This component counts up a number in an animated way. #react #reactjs
wtbob: I vouched for your comment to un-kill it so I can post this response here where it should be rather than in a descendent comment. First and foremost, I vehemently disagree with you. But I think you made your point in a civil manner and supported it with an argument, and for that reason alone you deserve to be heard and responded to with civil arguments rather than by censorship. I may not agree with what you say, but I will defend to the end of my karma your right to say it, even here, as long as you're civil and advance an actual argument.

So:

> Gender is an objective, physical, biological fact, not a subjective experience.

You are wrong about this. It is both a biological circumstance (though not nearly as crisp a dichotomy as most people think) and a subjective experience, and some people have a mismatch between their biology and their subjective experience. It is simple human decency to defer to how someone chooses to self-identify even if it does not conform to your prejudices about how the world ought to be.
This is the first time I've ever looked through an S-1 before, but in the Risks section they say:

We have a history of losses and we are uncertain about our future profitability

Is it normal to go public when being uncertain if you'll ever be profitable?
I'm sorry, your point is that you think, so therefore reality is so? You can't think yourself into a different sex, I understand that they do see themselves as male or female despite their physical characteristics, but that has no bearing on much whether we like it or not. And to answer your question, you are your configuration of you, whether anyone perceives it or not, including yourself. I guess it's turning a bit philosophical cause I'm sure you're going to come back and say the world is only what is perceived of it, but that's not what I believe.
Ask HN: What is the biggest fully remote company?
I was wondering if there is a limit in employees when you can't be a fully remote any more.
If the only way you can argue against them is to refer to some rules you made up, I agree.

In any event "retribution" is an overly simplistic way of looking at what Thiel did. It could also be interpreted as protecting future victims of Gawker.

Suppose someone stabs me, and I live. For whatever reason, they get away and continue to run around stabbing people. If at some point in the future, they attempt to stab someone else and I stop them, killing them in the process, is that killing in retribution or protection? Maybe both. It doesn't really matter so long as we can stop people from getting stabbed.
I came here to post the same thing.
Now, some projects do not have their documentation wrapped in Dash docsets.
You actually can, via (ab)using requestAnimationFrame. It's been a while since I did front-end development, but back in the day (...okay, 2014 ish) we'd batch DOM reads and writes, run through them the next time the frame was painted, and avoid multiple redraws. It was rather cumbersome, especially since reads had to be asynchronous, but it was fast.
> I'm finding it a little tough to tell whether the author is talking about putting the browser or the web developer in control of grouping DOM updates.

The Web developer (or library author). He is talking about an API.
I very much disagree. Even if they've ended up accidentally Turing complete (which, don't get me wrong, is bad), they at least guide you towards the right thing to be doing at compile time: simple, declarative transformations. I have never seen a macro system that wasn't immediately abused for unmaintainable clever-clever things, whereas this has only emerged ~10 years after Java introduced generics.
If you read the driver's own comments on YouTube, he did react to the situation in time. His decision of action however was in error. He decided to take partial control of the vehicle by grabbing the steering wheel to change lanes and merge right. What he needed to do was take full control of the vehicle by tapping the brake to disengage the cruise control aspect of the AP.
Build the Best Twitter Ads API Tool – $250k Grand Prize and Twitter Exec Access
"Unhackable" is an awful... strong claim. Link?
The company is a tool to serve the interests of the investors, there is no "good for the company" distinct from "best for the investors". (Good for the employees is a thing, but it's quite often not the same thing, and not what the company exists to serve outside of, e.g., labor coops.)
Why Carmakers Are Suddenly Investing in Taxi Apps and Ride-Sharing
Agreed (though for me it was a bit longer than a week)!

Knowing when to use borrowing over owned copies I think is vital as well. Once I started planning out what was going to own what my code became a lot simpler and I spent less time fighting the borrow checker in general.

Hopefully as rust evolves so will the tooling and the borrow checker. It seems like you could build some cool visual aids and/or debugging info into IDEs for novices who are new. --explain already sort of does this.
Depends on the crime, if you've nicked something from a shop as a kid or sold a bit of blow, who gives a shit? If it's a violent or sexual crime, probably not great to employ someone in a job where they can drive drunk people to places.
I really enjoyed reading that, thanks!
I'll suggest just ignoring this type of moral based statements structured as:

1- if A is true (meaning are you a good citizen or not?)

2- then do B

Hiding the fact that A is a emotional statement and can fit in lots of opposite cases and circumstances because is ambiguous and moral based, and "moral" is an elusive and unmeasurable concept.

Thus, A and B are presented as dependent variables without any proof of this, and in fact in most of the cases are unrelated.

"Do you care about animals (preyed by nasty tentacular predators)? then you really should eat octopus", works perfectly also.
At best one could argue that there's simply less women in these communities due to societal pressures. During the past decade or so I've probably met as many transwomen as "real" women on these hacker IRCs.

However, I do believe that women are just as likely and willing to participate when they do end up in these communities. It's just that they're less likely to do so, just as they're less likely to end up working as programmers.
We can't complain about individual (non-accredited) investors getting locked out of fast-growing tech companies and simultaneously complain when companies IPO when they've reached significant revenue but not yet hit profitability.

IPOs are a capital-raising event; if companies only did them when they were profitable they'd be no more than VCs cashing in after they've milked out all the good upside potential.
1) Investors in growth companies care about what's next, not what's past. The past numbers are important to lend credibility to projections, but nobody values growth companies based on (presumably much smaller) numbers from the past.

2) Also from TFA: "Snapchat’s revenues in 2015 were $59 million (recall that there was no real monetization effort in the first part of the year, and only the beginnings of it in the latter part of the year)."

I'm not privy to any internals at Snapchat, but based on the other metrics in the article, the projections are not implausible at all. But yeah, it's still not appropriate for people whose idea of risk is owning Procter & Gamble.
There are far more than 2 people here:

https://github.com/zfsonlinux/zfs/commits/master

I will admit that my contribution activity has been low as of late, but it will pick up again soon. As for the bug list, that is because basically all distribution problems get sent there and duplicates are not closed until it is proven that they are duplicates. There is no such transparency with other filesystems' bug tracking. Redhat receives plenty of bug reports through Fedora that they happily close if not solved by EOL.

As for btrfs, one of the btrfs developers claimed that ZFS has 5 times the development resources of btrfs:

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

As for lawsuit fears, the fact is that using any software at all puts you at risk of a lawsuit. Whether or not the plaintiff has a legitimate case is a separate matter. However, if we consider the prospect of Oracle having a case against those using btrfs or ZFS, btrfs would be at higher risk. The CDDL provides an implicit patent grant while the GPLv2 does not. Any ZFS patents that are applicable to btrfs that Oracle accquired from Sun could be used against those using btrfs. The repercussions for Oracle would be huge, but if we are discussing about the potential for legal issues with Oracle, then btrfs is at the greatest risk.

From what I know of the internals of the two, btrfs has far more problems. This shows some of the problems on an enterprise distribution:

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

The idea that performance can be so horrible that the system might as well have deadlocked is a severe problem. The ENOSPC issues from internal fragmentation is another severe problem. Then there is the lack of backports. I could continue, but I see no need.
> To ensure each test has a clean slate, we clear the database between each test.

The proposed solution to manually nuke the database state seems crazy to me. Some alternatives:

1. Run the entire test in a transaction, do flushes and assert as normal. At the end, ROLLBACK instead of COMMIT and now you have a pristine database again. [1]

2. Setup pristine DB state once and then use `CREATE DATABASE ... WITH TEMPLATE ...` to create a temporary database. Not sure what the perf hit is, but it's probably worth trying. [2]

[1] http://alextechrants.blogspot.ca/2013/08/unit-testing-sqlalc...

[2] https://www.postgresql.org/docs/9.4/static/manage-ag-templat...
CREATE DATABASE actually works by copying an existing database. By default, it copies the standard system database named template1.
What did I say that's conflicted?
I'm OK with violent offenders being effectively banned forever from transporting people alone in a car. In this case, the driver was "facing 17 additional...charges" including "weapons possession, arson, armed robbery, burglary, vehicle theft".
Minor UI feedback:

The settings UI is extremely hard to read on my screen. The headings are light grey on white, and no amount of messing with my screen's contrast settings leaves something easy to read.

The checkboxes also immediately convey "disabled" due to their coloring. Your UI in general is spot on and sanely designed, but please consider taking a cue from the OSX HIG[1] and use the system colors and leave the light grey stuff for actual disablement, it will make your app look a lot more native.

[1] (about halfway down the page): https://developer.apple.com/library/mac/documentation/UserEx...
This kind of language is very standard. The risks section pretty much always contains obvious platitudes ("An earthquake might destroy all our computers," "All our employees may quit").
I think best practice here is to run the whole test in a transaction and then roll back the transaction at the end. This is the approach Django uses.
Had no idea that WhatsApp was even a Twilio customer let alone one of its largest.

>We currently generate significant revenue from WhatsApp and the loss of WhatsApp could harm our business, results of operations and financial condition.

>In 2013, 2014 and 2015 and the three months ended March 31, 2016, WhatsApp accounted for 11%, 13%, 17% and 15% of our revenue, respectively. WhatsApp uses our Programmable Voice products and Programmable Messaging products in its applications to verify new and existing users on its service. We have seen year-over-year growth in WhatsApp's use of our products since 2013 as its service has expanded and as it has increased the use of our products within its applications.

>Our Variable Customer Accounts, including WhatsApp, do not have long-term contracts with us and may reduce or fully terminate their usage of our products at any time without penalty or termination charges. In addition, the usage of our products by WhatsApp and other Variable Customer Accounts may change significantly between periods.
Introducing Dayron – The Elixir REST client you ever wanted
Which only leads to more crime. It's a bad state of affairs considering how much of the US population is in prison (let alone large swaths of certain groups). That said, there are certain professions I'm not sure I generally want to risk a second chance: childcare, drivers, etc.
I'm not trying to bash Rust, i love it, so for random viewers looking to pick a fight.. please don't bother. I'm only citing what my experience thus far is.

It's confusing, as hell.

Let me try to explain a little bit. I'm a average dev, and have been for ~7 years or so. My languages have typically been dynamic, but the past 2 years has been heavily Go.

I picked up the majority of Rust, as well as basic borrow checker usage, in a matter of hours. But that's where the fun stopped. Generic syntax beat me up (mostly related to Static dispatch and Type Assertions). Lifetime syntaxes are currently kicking my ass as well. The problem as i see it, seems to be that i am a more.. "dig in" developer. And frankly, that does not seem to fly here. I've read a lot of the rust docs, but rather than start to finish, it's been in response to questions i have. This seems to be problematic for rust, as important concepts can be left in the dust.

A good example of this is Static vs Dynamic Dispatch is rust. Heavy trait usage combined with using Static Dispatch incorrectly resulted in code not designed for what i wanted, and lots of seemingly random bugs. Ie, `foo = Foo::new()` would fail, but `foo = Foo::new(); foo.bad(baz);` would succeed.

Currently i'm trying to figure out how to either move a variable out of a block, or, more importantly define a lifetime on `Ok(r) => r,` so that the result can escape the block.

Anyway. None of this is the fault of rust exactly, and again, i love this language. I'm switching because Go hasn't offered the full safety i want. But man, it has been quite the hellish experience to get started.
Yes, but the deficit/revenue is falling fast
2013: 53%
2014: 30%
2015: 21%
2016Q1: 11%
JavaScript Through Ruby Eyes
Back to Reddit with you.
If the driver had used it off-highway 1,000 times in the past, but then the Tesla made an error off-highway, is it Tesla's fault or the driver's fault?

This isn't even a Tesla issue: most car makers now ship cars with adaptive cruise control with stop-and-go. If they stop 95% of the time in this situation, do we really have to ban them because some drivers insist that past experiences constitute a valid test?
> I would think they care about diluting their brand.

They should, but nobody has sued them over this issue of widespread cheating yet.

Something similar happened at UNC when athletes were taking bogus classes [1], but the judge tossed out the case because the students waited too long to sue [2]

FIRE is a firm whose stated goal is to defend individual rights in education [3].

> At some point these degrees you say are worthless will mean people stop paying - don't you think?

Yes, if there's an alternative to college to earning a higher salary. But, most parents aren't advising their kids to get a blue collar job like Mike Rowe espouses. Parents want their kids to go to college. They're not as concerned about their kids' debt, and high school kids haven't yet learned to be wary of student loan debt. The moment they discover that student debt is a problem is the moment it's too late, when they've failed out of school or look for a job and can't find one.

Rather than pushing college upon everyone, we should be educating students about debt and other options. At the same time, we should be pulling back some manufacturing jobs to provide such other options. The US isn't going to survive on elitist service industries alone. We need to understand that while every human being is capable of very high intellect, every person in America does not need or want to be in the services industry. Obama has been pushing to recall manufacturing jobs [4], so that's a start

[1] http://edition.cnn.com/2015/04/01/sport/ncaa-response-to-law...

[2] http://www.charlotteobserver.com/news/local/education/articl...

[3] https://www.thefire.org/

[4] https://www.whitehouse.gov/the-press-office/2012/01/11/remar...
Announcing Rust 1.9
While we're at it, are safety considerations the only problem that prevented nuclear powered automotive engines? I've always wondered why.
- Hello, my name is Henrik.

- I disagree, I'm going to call you Steve.

- ???
Host it on SquareSpace!
Star Wars: Episode IV, The Massive Infographic
> [...] I remember being surprised that there was no way for me to group DOM manipulations into SQL-like transactions [...]

There is a way to group DOM manipulations: a DocumentFragment[0]. If you have a wrapper, you can easily use

parent.replaceChild(fragment, wrapper); // [1]

So long as you start with your fragment having a new copy of that wrapper—the entire node and its children will be replaced in 1 operation. Then layout and paint should only happen once apiece.

I've used similar techniques to make applications that render efficiently.

[0]: https://developer.mozilla.org/en-US/docs/Web/API/DocumentFra...
[1]: https://developer.mozilla.org/en-US/docs/Web/API/Node/replac...
I'd like to be on the team working on printing GIFs please.
In the details tab when you click on a particular entry, you can modify that entries productivity category, more so there is a checkbox to send that info to the developers. I believe this is the functionality you are looking for.
I really like my experience with rust so far also, but a few caveats:

* try!() Is pretty annoying

* Working effectively with C in non-lexical ways seems to involve some unstable libraries and still requires nightly rust

* Macros are safer, but can't do some things that C macros can. For instance, they are hygienic, which means you can't conjure up new identifiers. For that, you need a syntax plugin, which is very powerful but the APIs aren't stable yet. This goes to the previous point.

* A few annoyances, like warning when you don't use a struct field as "dead code". If I'm interfacing with C I probably need that struct field whether the rust compiler sees it or not, but I don't want to disable all dead code warnings for that.
I thought it was 'jo' or 'joe'. I run into a lot of Chicagoans and they pepper their speech with 'joe'. I was always like 'joe' who? Found out recently it is a stand-in for dude.
Little to do with profound social impacts, its all about how much the evidence contradicts what someone either believes or wants to believe.

Now people certainly can hide behind the idea that they only do so for profound social implications but by then they are just trying avoid acknowledging that they know whats being said is true.

there are always some socially unacceptable facts, the kind people either nod their head or just acknowledge silently. It comes from being in a society where truth is second to needs.
This is gonna be really dumb, but what's the difference betwen American and 'Merican ...
Why would an IPO be bad for the company and employees?

It's just another fundraising round, with new shares issued.

I guess you're suggesting that an IPO exposes a company to more of a herd mentality regarding immediate profitability which it wouldn't be exposed to in a private round of financing, and that it might be punished for it?
10ms latency is crap if you're doing something like realtime ad exchange bidding, where you have <60ms bid times. Really do not want that hiccup.
I am by no means an expert here, and IANAL, but in my limited experience, yes it is very common to see statements like that in filings. They have to disclose any and all potential risks to investors, and as basic as it seems that is a risk.
yeah, dragging components from the component list and seeing them immediately reflected in the simulator with live-reload is freaking awesome.
Lockheed-Martin's Skunk Works is trying to build a useful fusion reactor using a somewhat similar approach.[1] They announced this a few years ago, and last fall, their people gave a talk at the Princeton Plasma Physics Laboratory. (There's video, but it won't play in Firefox on Linux.[2])

It's striking that a very capable organization is working on this.

[1] http://www.pppl.gov/events/colloquium-lockheed-martin-compac...
[2] https://mediacentral.princeton.edu/media/Thursday+Colloquium...
I usually try to minimize the number of tests that rely on this (shared) DB state. So I'll focus more on unit and integration tests. Functional tests still do have value though. See: http://xunitpatterns.com/Testing%20With%20Databases.html

Where possible, I like to have data that can exist independent of the other data on the system. I can make a separate 'tennant' for that test - and just ensure it's wiped before I proceed. Sort of a multi-tennant approach. Works great. I don't bother with a 'teardown', but do any cleanup before the test runs. I also ensure the tests are written to not make assumptions about global state.

Instead of dropping all constraints as the article suggested (that sounds hacky), I use ON DELETE CASCADE constraints. If I miss some, the tests fail. Seems easy enough to maintain.

With the above approach, DB testing is approachable and still pretty quick.
I use the index as a sort of quasi-commit, which lets me effectively step back one revision if needed. I find this to be a lighter-weight option than many commits that may be meaningless, while providing probably 90% of what those commits would give me throughout the day. As a result I typically make 4-5 actual commits but may have had many transient points at which I could have - and sometimes did - revert a set of changes.
Dependency injection as a concept is not tied to a framework. Just inject your dependencies into constructors.

I occasionally do this even in languages with good DI frameworks like Java when I don't want to pull in a Guice or Spring dependency. Even "manual" DI like this is so much better than not doing DI at all.
That's precisely the point: if threads never block or yield the CPU, you can guarantee system-wide progress.

If you have an algorithm which might deadlock, 'progress' isn't really well defined.