3 ms·
I think this post is certainly correct in addressing CPU issues, and certain problems with Javascript. What it fails to recognize however is that the "how" of
by LukeWalsh 13y ago
I think this post is certainly correct in addressing CPU issues, and certain problems with Javascript.
What it fails to recognize however is that the "how" of Node.js isn't the cool part about node. The cool part is the "what" which is bridging the gap between the client and the server. This is the reason that people tolerate writing more javascript, not because everone loves javascript.
- voidlogic 13y ago>The cool part is the "what" which is bridging the gap between the client and the server. This is what loses me- how is that cool or good? I would much rather write a static html/css/angular frontend and have it talk to a Go webservice on my server. I want to use the best language for the client and server side, why do I care if they are the same? I want them to be basically completely independent apps where I could replace one or the other with a new implementation.
- davegb3 13y agoTrue, but there are cases when having the same language both sides can save some time, like validation routines for example. Not always appropriate, but can be a leg up on a project.