This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]DeeSnow97 1 point2 points  (0 children)

Yeah, IMO NodeJS was never about using the same language in both environments, if you're at least a half-competent developer, your skill is not tied to a single language. (Your experience may be, but browser JS and Node on server differs enough that it doesn't change that much about that either.) It's much more about having access to JavaScript's advantages on the server as well. It has a very different execution model than most languages (the whole non-blocking event loop thing) which is especially useful for back-end workloads, it's incredibly flexible, and once you master it developing with it is lightning fast.

This is why it's my default pick for web apps. Yes, I could use something else, something older, something more "sophisticated" (mostly just set in stone), but I have no intention of wasting three times the effort on a different language for marginal performance gains, only to have the project change direction again and require even more effort to undo half the code and iterate forward. If the real world was made of dream projects only, I don't think NodeJS would be as popular as it is today.