3 ms·
I have no problem what language or stack you use as long as you only compile it once, not every time you click something. There are energy and memory savings to
by hggigg 2y ago
I have no problem what language or stack you use as long as you only compile it once, not every time you click something. There are energy and memory savings to be made :)
It's definitely not better for content. It's impossible to reference easily, everything is transient and ephemeral, layouts differ all over the place, there is no concept of location other than anchors which are poorly defined, typography is "variable" and goes somewhere from hooky to crack smoking, still to this day half of the images are rasters, it's near impossible to save bits of it locally if you want to keep it, it's difficult to print and importantly the moment you add something dynamic to it you multiply the damage by 10x for all of the above.
- itohihiyt 2y agoIf you're talking simple content, text and images, and you're not trying to do "clever" stuff like making fancy transitions or anything that involves oodles of JavaScript then I can't see how the web isn't on par with pdf. I'd say it's better. I hate modern sites where you need JavaScript to load text and images. My issue with pdf is it's a shit show behind the scenes.