4 ms·
I don't think node.js per se is the worst thing. However, the way it is used, particularly what I believe to be a misguided attempt to do "full stack developmen
by vikramkrishnan 9y ago
I don't think node.js per se is the worst thing. However, the way it is used, particularly what I believe to be a misguided attempt to do "full stack development" is really terrible. And it is not the first time that we have made this mistake. The whole Java on the client side blew up in our faces.
If bosses really understood that client side and server side are two different problems with different mindsets and specializations we would not be in the world of pain that we are
- rektide 9y ago"However, the way it is used, particularly what I believe to be a misguided attempt to do "full stack development" is really terrible." I'm not sure what way you believe it is being used?
- vikramkrishnan 9y agoI am referring to the following mental algorithm I see being used by managers and some devs: 1. My front end guy does JS 2. My backend guy costs money 3. Let me remove 2 and get 1 to do both, it is all JS anyway; completely ignoring that the way you build the two is fundamentally different, with different mindsets. Language is just a small part of the equation. The claim that having a single language on FE and BE will save cash is simplistic and misguided. It is like saying since my kitchen utensils are built of stainless steel and aircraft carriers are built of stainless steel, I will get Le Crueset to manufacture my aircraft carriers