3 ms·
> Server-rendering of component updates is a post-SPA innovation (2018?), so it still seems worth explaining for most web developers. Absolutely not true. I wa
by dvt 4y ago
> Server-rendering of component updates is a post-SPA innovation (2018?), so it still seems worth explaining for most web developers.
Absolutely not true. I was doing this in 2009 and so were many other people (albeit through janky XMLHttpRequest via PHP polling ways).
- CharlesW 4y agoAgreed, it was super common. I'm attempting to say something slightly different, which is that SSR — as a technique that was codified, named, and supported in modern frameworks — first appeared around 2018 by my recollection, and so may be a new-ish concept for many web developers. My assumption is that the WebKit team understands their average web developer (which may be notably different than an average HN developer) enough to know whether an explanation is worthwhile.
- chrismorgan 4y agoIt’s a good deal older than that. If you’re talking about something like just React (the view layer), you can certainly go back well beyond 2010. If you’re talking about something more full-featured, like Next.js today, the oldest I can think of is Ember with its FastBoot, which was becoming usable by the end of 2014 and well-established by mid-2015 (even if 1.0 took until mid-2017—and there was a major internal restructuring to how building worked). https://blog.emberjs.com/inside-fastboot-the-road-to-server-side-rendering/ https://blog.emberjs.com/inside-fastboot-the-road-to-server-... is good background on that, showing also the attitudes of the time. https://blog.emberjs.com/tag/fastboot/ https://blog.emberjs.com/tag/fastboot/ for the other couple of posts about it.