3 ms·
> Not only this, but eventually we will ditch JS in favor of something more "isomorphic" with whatever the back-end is using. Why not use JavaScript itself for
by nitsky 6y ago
> Not only this, but eventually we will ditch JS in favor of something more "isomorphic" with whatever the back-end is using.
Why not use JavaScript itself for this? That is the strategy employed by Next.js/Nuxt.js/Sapper/etc. Your React/Vue/Svelte components are rendered on the server and then hydrated on the client.
- james-mcelwain 6y agoBecause Node.js isn't appropriate for a lot of back-end applications, or for legacy back-end applications that already exist.
- bcrosby95 6y agoWhy not just have everyone code in Javascript now and forever? Same reason we didn't settle with everyone coding in C. Or C++. Or Java. Or Python. The web is just a method of distribution. Not every problem or domain takes equally well to each programming model or language. It would be nice to be able to pick a tech stack that works for my domain and the characteristics of my project, rather than picking a tech stack because of how users access it.
- jerf 6y agoMostly because for all the development done on it, Javascript is still a %50 accurate name; it ain't Java, but it is definitely a scripting language. Node may be popular, but it's lightyears away from being able to say that it's chasing all the other languages out of the server niche, and it's been around for long enough that we can judge it's unlikely ever going to. In 5 years it's going to be a lot easier to get a non-scripting language compiled on to the client than it is to make a scripting language work as your sole backend language.