3 ms·
It's still absolutely baffling to me that anyone is willing to run JS server side. There are so many options which are much better suited, why are people willin
by bigstrat2003 2y ago
It's still absolutely baffling to me that anyone is willing to run JS server side. There are so many options which are much better suited, why are people willing to jam that square peg into the round hole?
- homebrewer 2y agoBecause they don't know and don't want to know anything else. Not a single polyglot developer I personally know have ever chosen JS for server side, not once.
- deleted 2y ago[deleted]
- sjamaan 2y agoPerhaps the siren song of "isomorphic JS", where you can run the same code on the server and on the client? I can see the use case for having complex model and validation code running on the client for speedy feedback and on the server for security, and perhaps also the idea you could render something entirely on the server when needed (eg for indexing and non-JS clients) and on the client when it's capable. Personally, I wouldn't want to touch server-side JS with a 10 foot barge pole.