3 ms·
> NPM is one of the reasons we've moved to Go for our server side code. It's one of the reasons, but far from the only reason. With Go, Python, Rust, Swift...
by malvosenior 8y ago
> NPM is one of the reasons we've moved to Go for our server side code.
It's one of the reasons, but far from the only reason. With Go, Python, Rust, Swift... is there any reason to use Javascript on the backend? Most attempts I see to "share" code between the browser and the server end up adding needless layers of abstraction and complexity.
- smacktoward 8y agoThe appeal of being able to use one language across the whole project, rather than one on the backend and a different one on the frontend, is very strong.
- malvosenior 8y agoI know the pitch for this is very strong but I've never seen any benefit in real life. Javascript was designed to be a client side browser scripting language, it's not equipped with a standard library that competes with other languages that were designed from day one for the server or systems programming. The skill sets of front-end and back-end developers are also very different. In my experience, when you use Node you end up with front-end devs programming back-end servers very poorly or you end up with back-end devs forced to use Node/JS. I've never actually met a seasoned back-end developer who would choose JS for the domain given no constraints.
- pier25 8y agoI think SSR is probably the best reason for using Node. Another one is making a GraphQL API that concentrates data for the clients from different places. It could be made in another language, but it's better if front end developers maintain that project. For bite sized cloud functions Node is also not a bad choice. But for pure backend projects, yeah, Node isn't the greatest choice these days.