| ▲ | bilekas 3 days ago | |
> Building a sub 512KB website is trivial. Even for larger sites, it can be trivial, but I prefer to look at it from a non SPA/state-mgmt point of view. Not every site needs to be an SPA. Or even a 'react app'. I visit a page, record your metrics on the backend for all I care, you have the request headers etc, just send me the data I need, nothing else. It doesn't have to be ugly or even lacking some flair, 500KB is a lot of text. Per page request, with ootb browser caching, there's no excuse. People have forgotten that's all you need. > People have forgotten that's all you need. Edit : No they havent, they just can't monetize optimizations. | ||
| ▲ | EMM_386 2 days ago | parent [-] | |
You don't even need a framework for a SPA. I have a SPA that is just vanilla web components and is clean, small, fast and tidy. No outside frameworks, just my own small amount of transpiled TypeScript. I prefer to write them that way because it meets my needs for the particular site and is very responsive. But I've also done PHP, ASP.Net, Rails and other server-side work for many years. Best tool for the job, and sometimes they are very different. | ||