JavaScript Client-Server Debate
The cluster discusses the pros and cons of using JavaScript for both client-side and server-side development (e.g., Node.js), including code sharing, necessity of server-side JS, and comparisons to traditional server languages.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Why not write all in Js then you don't need a server side? Plus much simpler code
The fact that it's not a server in your browser, but a client to a server on the backend makes it less of a server in your browser
No, he means the application logic should be on the server side, not in the browser. I doubt he has a problem with server-side Node.js.
Won't most Node apps still have client side JavaScript?
A lot of calculations may happen on the client. And the server may be written in JavaScript.
So how do you want to write your client-side? Does not using one language for both the server and client make sense to you?
Pretty sure the parent comment was talking about client side.
Just one of the many ways that modern Javascript baffles me - people pretend the client and server are equivalent.
You need a backend anyways. Shifting to a server-side codebase is eliminating duplication, and arguably server languages have better DX so win win.
Do you realise that if you only work with server-side code, you can't use client-side code?