2 ms·
You can inline the following in one HTML page: CSS (.css) JavaScript (.js) Plain Text (.txt) HTML (.html) SVG (.svg) Raster Images (.png, .jpg, .jpeg, .gif, .w
by DANmode 1mo ago
You can inline the following in one HTML page:
CSS (.css)
JavaScript (.js)
Plain Text (.txt)
HTML (.html)
SVG (.svg)
Raster Images (.png, .jpg, .jpeg, .gif, .webp, .bmp)
Audio (.mp3, .wav, .ogg)
Video (.mp4, .webm)
JSON (.json)
PDF (.pdf)
plus bring in other source resources as needed.
To answer your question:
The installer for GrapheneOS / Google Pixel phones is an “SPA” (or “webapp”).
I’ve seen bespoke fitness trackers of all kinds,
appliance control apps,
budget and pace-tracking stuff,
basically all of what computer programs used to do - before we started dynamically loading a ton of extra stuff onto the screen that nobody needed to do the task they came to do.
- preg_match 1mo agoRight, but if you’re dynamically changing the HTML from JS, like the graphemeos website does, then that’s client-side rendering, which is my whole argument. Embedding the JS in HTML makes zero difference, it’s the same thing. So, they are truly inseparable IMO. You can’t have a SPA without some amount of client side rendering, your example demonstrates that. So, what makes a SPA a SPA is the rendering. A SPA is “single page”, but only in literal meaning. Logically, every SPA is many pages, you just render them purely client-side.
- DANmode 28d agoAlmost every major website you interact with daily relies heavily on client-side execution to some degree. and none of this seems to have anything to do with the frontend being a single page.