Also there's nothing in (at least React's) server-side renderer that requires a Node runtime. You could run it in any JavaScript engine.
-
-
I assume the original tweet means not just Node but s/node/server-side JavaScript environment/. If your whole server stack is in Java or C++ or whatever it's probably nontrivial to add some JS engine into the mix
3 replies 0 retweets 16 likes -
-
Replying to @samccone @joshuaisgross
Sounds like Google should show us all how it's done and open-source their JS front-end framework with a runtime-agnostic (or just Java) render backend then
4 replies 0 retweets 27 likes -
Replying to @sebmck @joshuaisgross
Sounds like a great idea Calling
@cramforce
1 reply 0 retweets 4 likes -
I think that running JavaScript on the server for server side rendering is the right approach.
2 replies 0 retweets 18 likes -
The gap between right and practical is not something that can be bridged in many cases. :)
1 reply 0 retweets 3 likes -
Maybe many as in absolute but not many as in most. Those many will need to helps themselves. Mostly banks and other legacy corps. Companies like Google and Facebook can just run JavaScript.
2 replies 0 retweets 4 likes -
Replying to @cramforce @samccone and
*cough* Dockerfile with Rendertron *cough*
1 reply 0 retweets 0 likes -
Replying to @slightlylate @samccone and
That sounds like it would use a lot of electricity but sounds reasonable if you can't link to C++. I'd run a V8 that supports gRPC as it's only IO.
2 replies 0 retweets 4 likes
Worse Is Better (TM) (or so I've been told)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.
