In the end, that's what killed JS in the backend for me for anything nontrivial that needs decent performance. It gets you with things like "with its JIT, your

In the end, that's what killed JS in the backend for me for anything nontrivial that needs decent performance. It gets you with things like "with its JIT, your code might end up runnning faster than C" - and while that's true (!), it's going to come back biting your ass when anything falls out of the optimization loop. And this "something" always eventually happens, is often times a trivial one line change and will keep the whole team busy for three days until finally debugged and fixed. We're now building with Go. And while it's not the fastest language in synthetic tests, it's proved to be super predictable. If something breaks or leaks, it does so pretty hard (ever forgot a .Close() somewhere? :) and anything that's off is easy to discover and optimize with PProf. The V8 is an awesome and important piece of technology, but it's so complex that it's almost impossible to say why something worked out - or didn't.