I realize you are critical of that viewpoint, but point 2 seems really wacky to me. Current big project at work has a back end that is not in JS, but we still

I realize you are critical of that viewpoint, but point 2 seems really wacky to me. Current big project at work has a back end that is not in JS, but we still have a way to run the same validation code on both sides, which is run in an embedded JS interpreter on the server. I'm not sure I would want to write a complete back end in JS or not (even if I'm not in love with Java, lately), but reusing this part makes a lot of sense. --- We currently serialize (sync block) validation requests on the server through Nashorn, rather than having multiple instances (per thread or a pool). But, it's not like the requests wouldn't be serialized through Node, though. The rest of the request processing happens on independant threads normally. Not overly fond of threads, but I don't think I could get my team to by into Erlang or Elixir :-) For that matter, my primary partner on this project is a big Scala fan, and we couldn't even get the rest of the group to go for that :-(