Would be nice to have a `wake` function that cancels the timeout, rejecting the promise. Something like Angular's $timeout.
But I guess you need at least a bunch of lines for that.
Actually the object spread operator is part of ESNext, so no need to bring JSX up. And it's *so* much better than Object.assign to create immutable objects.
Basically,
const foo = { ...bar };
is equivalent to
const foo = Object.assign({}, bar);
but the former is more compact and readable than the latter.
If you mean that a language is a tool to program a computer so we're safe from using machine code directly, you may be right. But it's not what's commonly intended as a "development tool".
In the case of JavaScript, moreover, the language actually represents our final product, as the code is interpreted and compiled by the client on run-time.
That's the point: React doesn't have a state management layer. Which means you can choose the one that best suits your needs.
But also means that you need to make an additional effort to create a meaningful application. Will you use Redux or MobX? This freedom lessens the reusability potential of your components by a lot. What about the components you wrote just a year ago with Flux in mind?
But it's just one of the drawbacks of React. I won't list another, because the concept is: whatever looks cool now, will always have its flaws, and sooner or later something will come out that will make your current library look like crap.
Today we're all getting shivers when someone mentions "jQuery", but once it was the greatest thing since sliced bread.
There's no definitive JavaScript library. Libraries come and go. Only JavaScript remains.
React alone leaves quite a bit to be desired from medium applications and larger, though. One day maybe we'll feel the necessity of Redux or similar to be too much of a hassle.
I've always used double quotes, but mainly because I was already used to them from other languages (C, Java, Basic... you name it). When I became a JS developer I just stuck to them.
In PHP I mainly use single quotes, though, since I don't want interpolation by default.
It doesn't matter what you choose, just be consistent with it. And anyway, we'll soon be all using backticks anyway.
Still unfortunate.
JsPerf was one thing (and still is, as it seems to be on a rework) and this, although similar, is another. It sounds like hijacking the success of the former to grant success to the latter.
"JsPerformance", "JSBenchmark", "PerfJs"... there are a lot of names to choose from, copying an used one only because it's not protected by a trade mark doesn't sound nice to me.
Actually the object spread operator is part of ESNext, so no need to bring JSX up. And it's *so* much better than Object.assign to create immutable objects. Basically, const foo = { ...bar }; is equivalent to const foo = Object.assign({}, bar); but the former is more compact and readable than the latter.