skysight-inc/HackerNews huggingface dataset:
Not OP, but here's how I interpreted it:

"ES6" is what people used to call "ES2015". So whenever I see "ES6", I translate that to "JavaScript with a lot of features that JavaScript used to not have"

In the JavaScript world, some people "target" an older version (usually ES5) because for a long time, browsers and Node.JS didn't support "ES6" features. So while many have written "ES6", at least in the past they would have to "transpile" (read: compile) it, and the output is ES5 JavaScript (which many browsers can read).

But in recent times there has been an increase in people who aren't transpiling down to ES5; in other words, they give browsers their "ES6" code, and just hope the browsers understand it. OP is wondering why people would do that, and many responses here provide spectacular explanations.

EDIT: reading through responses, it seems many people interpreted the title to mean "Why do you write JS using things that debuted in ES2015 or after ES2015?". In other words, people ignore "targetting" and assume that everyone is still using a transpiler that targets ES5
> To find a parallel for the grossness and debauchery that now reign in New York one must go back to the Constantinople of Basil I.

H.L., honey, you have no idea...
Well wouldn't better driver's ed solve most of those issues? A tiered license system seems like an overly complex solution.

I've driven in both Germany and the US (DC area, while on holiday), and found US driving a lot more relaxed. There are some odd rules here and there, but in general it was less unpleasant. Driving on the Autobahn can be quite stressful when you have a few people who want to drive really fast. Those kinds of speed differences reduce road capacity significantly. I'm not saying these people are necessarily unqualified to drive at such speeds, they may be the best drivers in the world, but everyone would reach their destination sooner if those folks were to stick to 130-140km/h.

That said, the posted speed limits in the US are definitely on the low side. The same roads would have a higher speed limit in Germany.
How are they gonna get the model to snort Coke?
Exploring Pluto and a Billion Miles Beyond
Yeah, it shouldn't. I found this odd too.
Part of my thinking here is to get a dev environment that is 100% independent of my laptop - I don't need local files, or local configuration. Currently, I'm using Vagrant on a Mac, and that works well, but it's also wedded to a computer I'd like to put into semi-retirement, and I don't want to spend a fortune on a new one. The idea of just using cheap Chromebooks for dev sounds very appealing.
Another famous intellectual on humility toward Nature, Goethe:

Nature understands no jesting; she is always true, always serious, always severe; she is always right, and errors and faults are always those of man. The man incapable of appreciating her, she despises; and only to the apt, the pure, and the true, does she resign herself and reveal her secrets.
Instantly set yourself apart by crafting your narrative
> Why's it such a huge deal if your credit card gets compromised?

Because it's a pain in the ass.

You have to spend time with the bank to dispute the charges and get the card replaced.

It's also extremely common to get a new card number when they issue you a new card. So all the companies that have your card saved, won't be able to charge your card anymore.

And you might say "well surely it isn't that many sites" but it's still an effort to change your card details everywhere.

Then there are the "important but infrequent" charges, like a domain name renewal. If your card is cancelled and you forget to change your saved card, you'd better be attentive to the renewal notice or you'll lose your domain name.

I don't get why more banks don't let you generate a unique card number per merchant so if it's compromised it affects at most one place.
Had you considered that maybe that's not the only research ever done on the topic?

In fact, it isn't, and there are other polls and studies looking into opinions on topics such as execution of homosexuals. Again, a single search engine query could solve this mystery for you.
And in Java, anything deprecated is never really removed.
Yeah, but the Dash buttons are $5, or free with the $5 credit towards the first purchase...
Nuclide is not actually open source
As long as there was a standardized, transparent way to emancipate yourself and prove your readiness before that age, I'd support your proposal. In fact, why not get rid of the "automatic adulthood at given age" system at all so that everyone could attain adulthood only through the emancipation process?
That's interesting - will check it out in 2017. I got rid off a lot as well, but now that the dust has settled down, I am finding it increasingly hard to remember to not accumulate. It's a constant battle in this on-your-face advertising and consumption oriented constructs prevalent in society.
I've gone through the process of port forwarding my router and setting up dynamic DNS (who does that anymore? :) ) so I can hit my home desktop with an Ubuntu VM on it and I usually have a few AWS instances up at any given time for different projects. Then most of the active code gets synchronized between machines via Github.
> This is why I always have my visualizations overlay both failure rates and usage.

Do you have an example? I love having more viz tools in my toolbox!
From the article, it doesn't appear this has anything to do with quant models - they're looking to optimize how their employees conduct the work and how they are managed as personnel. This does not seem to target their trading strategies at all.
Disclaimer: I'm just a product/biz guy that codes on the side.

I started using CodeAnywhere earlier this year to manage a small PHP+mysql geospatial email system for an aviation charity I do the tech for...so wanted something cheap (its $120 a year?) and able to teach a non-tech how to go in and make a change (as I don't want them making edits in the github UI).
I was also using my Chromebook a lot while traveling and using shared space, so I needed a decent dev environment without Chrome plugins/jankiness/slowness from a 4gb system.

They have Android and iOS apps that make changes when on the go a touch easier, though code on a Nexus is pretty rough on a plane :-)

So far, pretty good - initially they were making changes to how containers were created and destroyed, causing some changes in the syntax of how a container is defined thus causing mine to be troublesome. However, their support was pretty responsive and got it sorted out.

gomix.com as mentioned here already is pretty new but has been reliable for me so far. It is a fogcreek venture so I imagine it will mature pretty quickly.
Very similar to my work here: https://github.com/lwansbrough/HolographicJS that got no love on HN. :(

But I'm really happy Microsoft has chosen to create something similar - I had hoped they would. Their implementation seems quite solid, I wonder if it supports libraries like Three.js yet.

If anyone is wondering why you might use this, the reason is pretty simple. Before this, there was only two ways to build HoloLens apps: Unity, or C++/DirectX. DX is great but slow to develop, Unity is fast to develop but requires a ton of prerequisite knowledge, and it consumes a ton of RAM. Baseline for this project will probably be similar to mine (around 15MB) whereas Unity's baseline in my experience is around 10x that at 150MB. This is substantial on HoloLens, because the maximum amount of RAM allotted to any application is 1GB.

I'm looking forward to seeing this bring web developers into the new world of MR. I'll be interested to see if this can be coupled with React VR for rapid prototyping.
Look at it from the candidate's point of view. Depending on what company I'm working for, I get 10, maybe 15 crappy days of paid time off that I have to split between vacation, sickness, and YOUR interview. If you take an entire day of my time, I can only do that max 10-15 times in the year, and that's if I don't get sick and have no vacation. I'm going to highly favor a company that does not make me blow one of those days entirely.

Multiple days? Not a chance.
Your newsletter is one of the best out there, keep up the good work. I like the minimalism and the one-liner summaries are exact and succinct.
I have to agree with Brian Bain on this one: Perhaps energy is a good place for you to look. Many solar companies should offer great returns for years to come and many oil and gas companies will likely be great buys this year as prices decline more.
Gravitational "batteries", aka moving large quantities of water uphill / downhill, can be pretty efficient, landscape permitting. A dam can also be dangerous if breached suddenly, though.

A really safe, auto-shutdown, no-meltdown, nuclear-waste-burning nuclear facility, e.g. based on molten Th salts, would beat solar in many areas. Needs significant R&D yet, like solar needed it 15 years ago.
Assholes, a Theory. https://en.wikipedia.org/wiki/Assholes:_A_Theory

Helped me understand why I object to assholes, and the real damage an asshole does to a group.

The sections on asshole capitalism, aka entitlement capitalism, are fascinating and relevant.
They have recently introduced centralized AP management called "Capsman" but it's still a little rough around the edges to set up. Their wiki has a lot of good info though, eg http://wiki.mikrotik.com/wiki/Manual:CAPsMAN

Roaming is very tough to get right unfortunately. Only the client devices can make a decision to roam, so without ugly hacks such as using a single channel / MAC / SSID to create a giant interfering WLAN, your options are limited. What you can do with Mikrotik is set up access rules to kick a client off an AP if the signal strength falls below a threshold, but as this is not client-initiated, there is a longer re-association time which could interrupt VoIP etc.
NixOS and nixpkgs is very functional, we use it in production at the company I work for and I also use it as my full-time laptop OS (it's great as a laptop OS).
Yeah but the checkout button on the insecure cart page could be changed so that it instead points to http://www.apple-payment.com/... or any random malicious "checkout" page which then steals your CC. They've compromised the security of credit card details users will at some point enter by doing this. It's insane if that isn't a priority.
Tufte wrote an essay on how the data available suggested that there was a high likelihood of O-ring failure, but that the data and findings were poorly communicated. This led to the decision to launch, the subsequent failure of the O-rings and loss of life. This essay appears in the booklet "Visual and Statistical Thinking"[0], among other publications, along with an other essay on how the source of cholera was traced to contaminated drinking water in 19th century London by John Snow. He plotted cholera cases on a map, and looked at where the outbreaks were most frequent.[1] This also led to the discovery of the vector of cholera, which up until then was unknown or at least misattributed. Both are great reads.

[0]: https://www.sfu.ca/cmns/courses/2012/801/1-Readings/Tufte%20...

[1]: https://en.wikipedia.org/wiki/1854_Broad_Street_cholera_outb...
My university has a course (maybe in the business or statistics departments? I'm not sure, as I didn't take it) that has a project where the professor gives this very pre-launch data to groups of students in a totally different context: It is presented as Formula One race data, and the task is for the students (the racing team) to decide whether or not to pull out of the important race based on current weather conditions and the potential safety implications for the driver.

The next class period, only after the teams propose their decided course of action, it is revealed where the data really came from. I imagine it's quite jarring, especially for those who decided to proceed, albeit with different risks in mind.
Is there a good way (besides commenting) to save posts like these to find later?
The Eldritch World of US Security Agencies
Agreed, this would be the best way forward IMO. There is a benefit to shipping applications if you have a need to access other system level APIs. But for the general use case of rendering, well, it's a bit of a hassle to have to create an app.
I was only 5 when this happened, but I remember what a blow this was to my school. Were past missions, like the Apollo's, dismissive of concerns like this as well and just lucky? Or was the shuttle missions just more complex, with more points of failure to be concerned about?
http://www.urbandictionary.com/define.php?term=botkit go for it! define it.
It's not an "entire class of jobs" that caused the situation. The parent and/or student purposefully made the decision to get mired in dtudent loan debt to go to a "selective private college", knowing that the pay wouldn't be good.
I think this....

> Mr. Dalio returned to run Bridgewater earlier this year after stepping back to a mentor role six years ago.

Is what's driving almost all of his new found desire for a unified AI to run everything.

Here you have a man who by any measure has been wildly successful, he tried stepping back and letting other take over but ended up finding that the team he left in charge didn't make the exact decisions he would have.

If the story ended there it wouldn't be in any way surprising, who hasn't left a team and second guessed the decisions that the new leaders have made.

It turns out that when you are worth 15 Billion one of the things you can do is hire a shit load of AI experts, like one of the heads of IBM's Watson team, to build an AI to make decisions based on WWRDD, "What would Ray Dalio Do"?

Since his first retirement failed, this is his new take on how to have his second retirement go smoother. Just build an AI that bases all decisions on the Bridge water principles that he wrote down years ago.

see: https://www.principles.com/

As an aside, he recently let Tony Robbins publish his ideal portfolio, the all weather portfolio. It's actually a pretty strong portfolio for the average person.

http://awealthofcommonsense.com/2014/11/back-testing-tony-ro...

http://www.moneysense.ca/invest/raining-on-the-all-seasons-p...
Recently I've been advocating a move to distributing uncompiled ES6 packages, and shipping ES6 to browsers that support it and compiling using a single simple preset (ES2015 except modules).

There are several big reasons:

1) ES5 "classes" cannot extend ES6 classes (it's not possible to emulate a super() call in ES5), so:

1a) All the extendable built-ins are basically ES6 classes. If you want to extend Array, Map, Set, HTMLElement, Error, etc. you really should use ES6, and deal with emulating extending those classes in the compilation step.

1b) Really useful patterns, like ES6 mixins ( http://justinfagnani.com/2015/12/21/real-mixins-with-javascr... ) don't work when ES5 and ES6 versions are mixed in a prototype chain. That is, an ES6 mixin, compiled to ES5, can't be applied to an ES6 superclass. So if you distribute ES5 you're forcing everything above you on the prototype chain to be ES5.

2) It's much easier to debug uncompiled code, and all major browsers (as of Firefox 51) and node support ES6 well. Shipping uncompiled ES6 is a dream to work with comparatively.

3) ES6 is a much better compilation target for things like async/await because of generators.

4) ES6 is easier to statically analyze, so tools like TernJS and TypeScript (which can do analysis of regular JS too) can give better completions, etc.

5) It makes the pipeline from source -> packaging -> depending -> building for deployment much simpler.

Packages shouldn't assume too much about their eventual environment. That used to mean not assuming that the environment had ES6 or things like Promises. But times change and now that all the current environments support ES6, packages shouldn't assume that environments _don't_ support it.

So packages shouldn't directly depend on polyfills that most current environments have (Promise, Object.assign, new Array methods, etc.). Instead they should target standard ES6 and let the app developer who knows what they're targeting choose the necessary polyfills and down compilation. There's really too much bloat from packages forcing the inclusion of multiple Promise polyfills, or versions of core-js.

Also, it used to be that compiling dependencies was a major pain. You'd likely have to write custom build rules that compile and stage each dependency - because each dependency might have different language features and polyfill they might use. Now the packagers like WebPack and Rollup are so good at finding all dependencies statically, and we have a new stable plateau of language features in ES6, that the packager can compile everything it needs.

Of course if you use features beyond ES6, then those should be compiled to ES6. This implies a rule of thumb to move forward: Once all major browsers and node LTS have a feature, start assuming that feature and don't compile it out. For example, once Firefox and node LTS get the exponentiation operator, start distributing ES2016 (see http://kangax.github.io/compat-table/es2016plus/ ).
Nice, I work on similar sorts of projects, but I run a Python shop :)
Crocodiles (and Polo Ponies) Go Missing as Scalpel-Wielding Consumers Revolt
Could you quote it then? Cause I can't find it.

If you mean table 3, make sure you read the following associated quoted part:

"This statistic is affected by two factors: youth turnout and the age structure of the whole population. (Youth share could rise, for example, if turnout remained constant but
the population became younger.)"

Also, my quoted data is from 18-29, and approx 40-51%. If 18-24 is only 6-9% then the group from 24-29 is either far smaller, or is having some really insane turnout of more than 71%.
I just finished The Phoenix Project recently, and I thought it was great. It is effectively a novel about a large software project which is being mismanaged and on the brink of failure, and the steps that the team (and related teams) took to save it from the grips of death. The point of the book seems to be to explain the types of situations that are improved by focusing on devops and agile development.

Personally, this book really hit home, as I had recently left a team/project much like the one described in the book, however I think anyone working on a software project at a decent sized company will be able to relate to many of the problems presented early in the book.
There is a plan to start deploying Watson-like AIs in the legal field to automatically data mine for precedents and other legal resources.

> Why does the person putting together my will or litigating a suit for me need to be backed by an organization with an office building, expensive executives, etc?

These exists because they are currently necessary (they are the "tools" you speak of) but they're a pure business cost and constantly under pressure to not exist. Computers have already reduced this back-end cost immensely. For example, lawyers these days all use dictation software rather than having a secretary write out shorthand. If all the tools can be automated, they eventually will.
1. Nexus (Ramez Naam)

2. Infinite Jest (David Foster Wallace)

3. The Fellowship of the Ring (J. R. R. Tolkien)

4. The Sin of Certainty (Peter Enns)

5. The Bible Tells Me So (Peter Enns)

6. Thomas Traherne, Centuries of Meditations

7. Neverwhere (Neil Gaiman)

8. Elantris (Brandon Sanderson)

9. A Wild Sheep Chase (Haruki Murakami)

10. Colorless Tsukuru Tazaki and His Years of Pilgrimage (Haruki Murakami)

11. Freedom TM (Daniel Suarez)

12. Lightning (Dean Koontz)

13. Daemons (Daniel Suarez)

14. Foundation and Earth (Isaac Asimov)

15. Something Wicked This Way Comes (Ray Bradbury)

16. Fear and Loathing in Las Veges (Hunter S. Thompson)

17. Foundation's Edge (Isaac Asimov)

18. The Doors of Perception (Aldous Huxley)

19. Cryptonomicon (Neal Stephenson)

20. Tortilla Flat (John Steinbeck)

21. The Diamond Age (Neal Stephenson)
> some (maybe most?) black box quants own their algorithm even if they leave the Hedge Fund.

I've never observed this be the case at all.
"Hit a nerve - a prized attribute." It would be interesting to see how quickly the company as a whole (and the system, if possible) responds to the results of incentives. Does the culture quickly regress to fooling the algorithm or does a cat and mouse game result?

Either way not something I'd want to use to drive culture, but an interesting take on how to "institutionalize" a culture and cultural norms even long after one has left the business.
I actually thought it was horrible and lazy. I thought of Eggers as a "literary" author, but the writing quality was low, and the plot unimaginative. It was like reading a thin script for a bad action movie.

I also read Ed Catmull's "Creativity Inc." this year, and one of the things he talked about was research trips for artists. He said that even if the audience of Ratatouille didn't know what the inside of a high end French kitchen looked like, it would come through in the movie that the ARTISTS did know. He emphasized the importance of these trips in the book.

Having worked in Silicon Valley, it felt like Eggers basically read a bunch of newspaper articles about it and then wrote a book, rather than visiting the place and talking to people. If you want to write a dystopian novel, this area is certainly rich with possibility. I remember that 10+ years ago I was astounded at how well "Microserfs" captured the mood and motivations of people... I'll have to go back and read it again.
That's incorrect. Car was in autonomous mode when it ran the red light.
It shouldn't be surprising. The whole point of Facebook is sharing information. Not much point to a social network if your friends can't see a thing you post. Permeable membrane is permeable.
I'm also a big c9 fan. On small systems I've also used Codiad which can be easier on RAM if you're running apache.
Is it actually allowed to use ML in an autonomous vehicle?
If you're interested in a good overview of Architecture in the context of period art/philosophy (and culture in general), it would be hard to recommend Kenneth Clark's Civilisation [0] series more. It shows the development of architecture through the ages in context, and he has extremely interesting and insightful views on what that says about the human condition of the people living at the time.

[0] https://en.wikipedia.org/wiki/Civilisation_(TV_series)
> The OP was engaging in discussion, not seriously advocating a course of action.

This is an important distinction to make, but it's not a black-and-white one. And while OP didn't literally say "I think we should take rights from 18-24 year olds", they do seem to be arguing in that direction.

> When you're older, you won't take offense so easily.

Please don't condescend.
> It would cost way more than the value of the actual product.

Shipping from China is already subsidized by postal rates from the rest of the developed world[0]. Shipping in a container on a boat isn't free, and probably costs more than you pay now when buying something from China:

"As part of this reform process, China will be transitioned in 2016 into a category for more developed nations, who generally pay higher terminal dues."

[0] http://fortune.com/2015/03/11/united-nations-subsidy-chinese...
Good thing to do, but makes me think how much more effective (in terms of help given per dollar spent) it would be to help these people in some other place where the costs of living are much lower.