2 ms·
> What are its advantages? > There is only one rendering engine, cutting down complexity. Actually there are 2 rendering, the server sending HTML and the brows
by simon84 2mo ago
> What are its advantages?
> There is only one rendering engine, cutting down complexity.
Actually there are 2 rendering, the server sending HTML and the browser drawing it on your screen.
So why not push the logic and send a jpg image of the rendered content itself. Lol
The whole concept of decoupling the frontend and the backend is that they can be agnostic of each other, they need to align but it is not the same skills/concerns.
Serve rendered html like in 2000 and you have recreated a smart way to do what industry spent decades running away from.
- mikestorrent 2mo agoThere are proxies to enable old computers with old browsers to render the modern web as an imagemap. And of course, 20 years ago I was doing everything you'd want to do with a modern webapp with PHP; fast enough for a thousand users on a dual CPU Xeon.
- jdkoeck 2mo agoAccording to your logic, front end apps thus have three rendering engines: the server (rendering json), the browser, the JavaScript framework. Count the rendering engines like you want, the point still stands: server rendered apps are architecturally simpler. There is no one size fits all solution. Frontend-heavy projects have their place, server-rendered ones too.