4 ms·

Your description of nested call backs sounds terrifying. I don't think the issue here is with the language, but rather your approach to it. Nested callbacks can

Your description of nested call backs sounds terrifying. I don't think the issue here is with the language, but rather your approach to it. Nested callbacks can be a pain, but it seems like the solution here may be to ensure that you properly handle your errors rather than expecting everything to continue to work when everything goes down -- seems like a safer approach to me. Even so, many newer features in javascript involving Promises and async/await can help you avoid callbacks, so the nested call backs isn't really an issue. I'm curious -- what's your issue with Java? It's very different from Javascript, and the concurrency models are vastly different?

cutler 9y ago
My issue with Java is its lack of expressiveness, its culture of verbosity and that everything must be a class. Kotlin is a big improvement but the typical Java programmer is very conservative so unlikely to adopt it.
cutler 9y ago
Promises and async/await are really syntactic sugar. The error handling issue still remains. My original point was that Node.js is the least universal platform I can think of. Sure, you can attempt all things with it but it's not optimised for anything other than lightweight orchestration.