It perplexes me how every modern web framework that supports server side rendering couples itself to a node runtime. The reality is most companies cannot simply add a node runtime to their production environment.
I’m super curious. Maybe a gap in realizing _all_ server runtimes could in theory be used to piece together the output - and just starting from “our framework is JS so in order to SSR evaluate it you need to evaluate JS using our framework”?
> most companies cannot simply add a node runtime to their production environment.
A lot of companies are already running Node so the integration is trivial. I think you're extrapolating to big companies though with complicated release processes.
Yeah, it seems unavoidable unless you want multiple rendering implementations which doesn’t seem very desirable. Also impossible to pick a single language that everyone runs on the backend. JS seems close enough.
Node uses C++ engine (i.e. v8), so adding C++ JS runtime to a C++ project shouldn't be an issue. Java used to have Nashorn (deprecated in JDK 11, though), and I guess the current way to go in Java would be GraalVM+graaljs.
Glad you find it useful! I also saw github.com/samtgarson/vue…, although it relies on node, it still lets you build rails apps and just enhance it with Vue, while having full server-side rendering. Could potentially also use a Ruby JS interpreter like therubyracer.
Well, most companies think innovation is an afterthought. Which their failure to adapt their business to new technologies only create more opportunities for their competition to capitalize. These aren't restrictions, it's leadership failure.
A path that could be considered is a component model where only the template is required to render on the server - which then can be translated to any language. And the actual JS component code attaches itself on the client. Otherwise you need some JS engine on the server.
You can render HTML in any way you see fit on the server and then let the front end rebuild the virtual DOM from that.
I've done it with Vue, and I imagine it's perfectly possible with React and other libraries.
Oh man tell to me about the perils of trying to do SSR in Nashorn... Lot of teams hesitate to put in an additional layer just to do SSR... An idea I've been trying to propose is explore using cloud functions to at least reduce infra headache
Every modern framework that supports server side rendering offers using the one language to define components and their logic as a feature. No need to redo the components twice like it was done before Node (e.g. server PHP + browser JS).
I don't see why they can't simply add a node runtime to their production environment unless they don't own it or something.
But I'd be interested in the performance boost (or lack thereof) of doing SSR in a compiled language vs Node.
So I recently tried out Nuxtjs and generate static HTML ahead of time. Then serve the rendered stuff with a CDN. That gave me a pretty good lighthouse score. I think doing something like that is a good starting point.