Looks like this has been fixed.

Sounds like a great idea. Or maybe make the bar a link to the relevant story.

Looks like the actual article only mentions spiders rather than all arachnids, but I wonder what the total would be if they tallied mites' consumption as well?

Is this the ARES you mean? http://www.aresnorthamerica.com/

Love that they call it the ‘Sisyphus Railroad’.

_.get() is the killer feature of lodash.

Having never heard of Aurelia before, I was curious how this compared to React and found this interview with the creator/lead, Rob Eisenberg, with his thoughts:

https://medium.com/hashnode-insights/rob-eisenberg-on-aureli...

Also includes his comparison to Angular.

Haus | https://haus.com/ | San Francisco, CA | ONSITE | FULL-TIME

We’re a small, well-funded, early stage startup tackling the $50B+ market of residential real estate looking to bring on our third engineer.

Node backend, React + Redux + ES6 + etc frontend. We're looking to hire an experienced full stack engineer who is excited about a collaborative, inclusive environment to produce high-quality code. Learn more about our technical thoughts and approach on our eng blog here: https://engineering.haus.com

https://haus.com/job?id=245327

You can see the requirements in the link above, but here are a few non-requirements:

* Identification with a particular gender, race, or national origin.

* Sharing the same hobbies or beliefs as the other members of the team.

* A certain level of activity on a Github account.

* A minimum reputation level on StackOverflow.

> Such an instance is sometimes called, simply, a bar.

Kinda funny that a product that was only officially announced today already has a vernacular. :)

Probably the vernacular they've been using internally for the last year during development.

It reads more like a legal document.

This is a nice, non-trivial, but not too big project in react and redux:

https://github.com/andrewngu/sound-redux

Pretty nice commit history, this actually could be used to learn.

It is! It's part of a tutorial

Anyone have a good summary of the language feature changes & APIs (either standards or standards track) that are in the version of V8 that ships with Node 7 vs Node 6?

Expect a blog post shortly, but from v8 we get these language changes:

- await/async behind flag (already covered in thread)

- Exponentiation operator:

  > console.log(60**2*24);
  86400

- Object.{values,entries}:

  > o = { a: 1, b: 2}
  > Object.values(o);
  [ 1, 2 ]

- Object.getOwnPropertyDescriptor(s):

  > o = { a: 1 }
  > Object.getOwnPropertyDescriptors(o);
  { a: { value: 1, writable: true, enumerable: true, configurable: true } }

Additionally, there's a lot of pretty impressive optimization work done by the v8 team. You can read more about that on their blog: http://v8project.blogspot.com

Finally, one of my favorite things about Node.js 7.0 is the WhatWG http parser: https://github.com/nodejs/node/pull/7448.

edit: elaborated on exponentiation operator

Mind explaining what's whatwg URL ?

afaict, this is a parsing library implemented to fulfill WHATWG's spec for URLs. https://url.spec.whatwg.org/

60224 == 60^(224) ?

exponents are resolved first

From what I read in slack: Do not use async/await yet (with --harmony-async-await flag) because it has memory leaks (V8 5.5 will fix it when it gets added)

Is it known how easy it is to trigger the memory leak?

I came across this just the other day..

https://github.com/MatAtBread/fast-async

As a not-elligible-for-LTS version, it's probably fine - you're not going to be using Node 7 in production anyway, as it's only ever a cutting-edge release, unless you don't care about stability in which case memleaks are part and parcel.

http://node.green tackles this pretty well.

graceful-fs v3.0 is dead. This can bite you if you haven't updated gulp, less, npm, bower or similar in a while