4 ms·

There is also the code reuse factor. Why learn/use yet other language if you can use javascript for both server and client?

• jpiet 16y ago
  problem is: you cannot use it for both server and client. if this were true you would've been right. with node.js you still need to be aware if you're coding client or serverside for some constructs.
  • jrockway 16y ago
    Not really a problem; clients and servers always use different APIs in other languages. JavaScript is no difference. The advantage is that you get to use the same tools for client-side development and server-side development. Testing tools, interactive development tools, editor tools, etc. When you don't have to build your toolchain twice, you can make your toolchain twice as good. In theory. Javascript needs namespaces and modules before it will be useful for real work.
• gurraman 16y ago
  Better yet, let's go back to using ALGOL or something. Imagine how many reusable components we could have mustered up. We'd best stop all this innovation right now before it's too late.
  • maushu 16y ago
    Hmm, browsers don't use ALGOL though, better stay with JavaScript.
    • gurraman 16y ago
      Yes, but if the old geeks had been arguing like you did, the browsers would probably only support whatever language was popular on the server-side at that time.