3 ms·
Why all the JS/TS though? Part of what's great about a static site is serving simple HTML/CSS pages that look great, degrade gracefully, and don't hog users CPU
by southerntofu 5y ago
Why all the JS/TS though? Part of what's great about a static site is serving simple HTML/CSS pages that look great, degrade gracefully, and don't hog users CPU/RAM like JS applets do.
- nikivi 5y agoWith Next/Svelte/Remix you can only ship HTML/CSS if you want. Reason to use those frameworks is that I find their mental model to fit nicely for progressive enhancement. For my blog, I plan to have interactive content via MDX or something similar so there will always be optional JS involved.
- southerntofu 5y agoThanks for the clear answer. I've previously heard of server-side rendering for JS frameworks but i was certainly not aware that several frameworks supported it, and that some people like you actually cared :)
- gitgud 5y agoTake a look at nextjs it serves plain HTML and CSS then hydrates it with JavaScript interactive-ness