4 ms·
> If you know how to quench fires like this one: http://techblog.netflix.com/2014/11/nodejs-in-flames.html http://techblog.netflix.com/2014/11/nodejs-in-flames.
by atmosx 11y ago
> If you know how to quench fires like this one: http://techblog.netflix.com/2014/11/nodejs-in-flames.html http://techblog.netflix.com/2014/11/nodejs-in-flames.html
Awesome article, thanks for sharing. However, doesn't say much about JS per-se. The problem was a bug in Express.JS (see here[1] the resume) not in JS :-)
[1] http://www.infoq.com/news/2014/12/expressjs-burned-netflix http://www.infoq.com/news/2014/12/expressjs-burned-netflix
- lollipop25 11y agoWell the point was: - At some point, you'll eventually offload most of the JS effort to pre-exising modules that will more or less have bugs like this. And these kinds of bugs aren't apparent during development, or on a controlled environment. They happen on a production setting, which is at times hard to replicate. - JS is a terrible language in terms of debugging. There's no "compile time errors" to kill half of the bugs early. The best that tools at the moment could do is infer types based on static analysis, but that's it. If code is written in a very dynamic fashion, then you keep these tools guessing.