3 ms·
1. Runs on both front- and back-end. 2. Loads of people are familiar with it. 3. Isn't that bad if you know what you're doing with it. There's a cost to all of
by matthewmacleod 12y ago
1. Runs on both front- and back-end.
2. Loads of people are familiar with it.
3. Isn't that bad if you know what you're doing with it.
There's a cost to all of this, and there are better options. But it's really not hard to see why Javascript is gaining traction on the server side, as rubbish as it is.