12 ms·
I'm someone who builds a lot of SPAs for things that really don't need to be SPAs. The ability to host on gh-pages and to not implement a backend at all seals t
by Swizec 10y ago
I'm someone who builds a lot of SPAs for things that really don't need to be SPAs. The ability to host on gh-pages and to not implement a backend at all seals the deal for me.
That said, I try to load a static version of the compiled result as part of the skeleton HTML. Even if it gets overwritten by the SPA afterwards, it makes things look faster.
- codedokode 10y agoStoring and processing data locally in a user's browser without using server API actually can be a valid reason to build a client-side application. But they just use one megabyte of JS code to implement client-side rendering for JSON data received from API. Serving a 10 Kb HTML page is obviously a better solution. I see no single benefit from using complicated JS framework here.
- noxToken 10y agoExperience? Everyone is talking about X, but I've never used it. Perhaps I can build something simple just to dip my toe into X.
- JusticeJuice 10y agoPreach. Static client all the way.
- kejaed 10y agoWould you mind sharing any frameworks you use, specifically wrt ones that work well when hosting on gh-pages? Thanks.
- Swizec 10y agoI like to put things together with React. It's surprisingly good for static-ish landing pages because you can shuffle things around quickly once you have a few basic widgets built. When starting from react-create-app it's also super easy to deploy to gh-pages: npm run deploy It's really beautiful to work with and getting better every week.