4 ms·
Having the same language on the client and on the server is a huge productivity booster for me. I can’t imagine writing so many things twice again. Have you tri
by zoul 2y ago
Having the same language on the client and on the server is a huge productivity booster for me. I can’t imagine writing so many things twice again. Have you tried it?
- samaltmanfried 2y ago[dead]
- pjmlp 2y agoUnfortunely I have to, thanks to the Next.js and React only SDKs, that many SaaS products now have as extension mechanism. Also if it is such a great experience, people wouldn't be rewriting the node ecosystem in Dart, Go and Rust.
- dgb23 2y agoIt’s not necessary to use the same language for that. In many cases you can achieve the same with a clearer separation, with data driven methods and by generally not running so much JS. The typical example is input validation. You want immediate feedback on the client, but obviously you validate on the server. But instead of running literally the same specific code twice, you can use json-schema or your own general data description of what valid input is. You move the specifics from code into data.