4 ms·

> Javascript frameworks are amazing and can provide a much richer, much better experience. I think this is the point worth inspecting if you're considering ser

> Javascript frameworks are amazing and can provide a much richer, much better experience. I think this is the point worth inspecting if you're considering server side rendering. If you're making a page that just displays content, I don't see any reason to throw Javascript in front of it. Just render your HTML and send it. If you want to make changes to the content dynamically, if it's going to take super long to load and you want to show users a loading screen, if they can interact with the content, etc, that may be a case to throw Javascript into the equation.

aclimatt 10y ago
This is incredibly true and something you don't realize until you're browsing the web on a slow connection. I was travelling with 2G and using most client side apps was near impossible. One app sent down a 1.9MB `components.js` file, and because it was a JS app, all scripts had to be loaded until anything rendered. Obviously server-side apps are in no way immune from this, but by default, unless you really do need a rich client experience, it's often not worth the bundle size and CPU load. Just send down HTML. You know which website works fabulously over 2G? Hacker News.