FYI: Idiomatic Javascript / Builtins should be fast with the recent revamp of the V8 engine (stop writing "CrankScript").<p><a href="http://benediktmeurer.de/2017/03/01/v8-behind-the-scenes-february-edition/" rel="nofollow">http://benediktmeurer.de/2017/03/01/v8-behind-the-scenes-feb...</a><p><a href="https://github.com/v8/v8/wiki/TurboFan" rel="nofollow">https://github.com/v8/v8/wiki/TurboFan</a><p><a href="https://www.youtube.com/watch?v=M1FBosB5tjM" rel="nofollow">https://www.youtube.com/watch?v=M1FBosB5tjM</a>
Ok, seems like an interesting article but what the hell is up with those share icons. On your mobile if you rotate the screen to read the interesting table they cover up the first damn column. Then you rotate it back to portrait and they don't move back.<p>Fix your website. Remove those silly icons!
The new major version 8 of Node.js coming out in April will be a great performance booster for those who started using async/await and more:<p>- Node upgraded v8 to 5.7 [1] & async functions as fast as promises [2]<p>- Optimizations in fs[3]<p>[1] <a href="https://github.com/nodejs/node/pull/11752" rel="nofollow">https://github.com/nodejs/node/pull/11752</a><p>[2] <a href="https://v8project.blogspot.ca/2017/02/v8-release-57.html" rel="nofollow">https://v8project.blogspot.ca/2017/02/v8-release-57.html</a><p>[3] <a href="https://github.com/nodejs/node/pull/12105" rel="nofollow">https://github.com/nodejs/node/pull/12105</a>
According to the table, there are an increasing number of constructs that prevent optimization. The oldest versions of node seem to have no constructs that prevent optimization. Can that be right?
I find the (repeated) use of the word polymorphism here a bit confusing...<p>I'm mostly used to it an class inheritance-related contexts. Is it used differently in the Node/JS-community?
I'd really like to find a position doing more Node development. It seems like every place in my area that claims to just uses npm. I've had to learn the MEAN stack on my own, and it feels like it outperforms a lot of the apps I've built in other stacks.
A quadratic algorithm optimized by v8 will be still quadratic.<p>While these optimizations can be helpful, real problem is order of growth. To optimize order of growth problems knowledge of algorithms and data structures is important.<p>Optimization can be assisted by instrumentation and profiling.
> the JavaScript engine will not accept to optimize it<p>What does this mean? I don't understand if it's good or bad. Sounds bad but seems good according to the table?
Unrelated and I'm sorry for that, but do you know of a good way to get rid of the scroll hijacking? I didn't find a lot of extensions for Chrome and the one I tried wasn't working.<p>It blows my mind to encounter this bad practice on a developper related website.