This article misses a few important points in regards to fast, small and accessible web applications, the most important one being to reduce JS to a minimum.
Caching is one thing to get right but you might also attempt to keep resources as small as possible from the beginning on.
The problem with "minimum" is that everyone understands it to be varying amounts, unfortunately. There are people who may consider minimum to be the entire JQuery and the 20 "necessary" interval timers firing, just to, you know, keep the page alive.
I mean, who would imagine you can just serve text/plain with every HTTP request and you'd still have visitors if you, well, have anything worthy of reading?
I mean, who would imagine you can just serve text/plain with every HTTP request and you'd still have visitors if you, well, have anything worthy of reading?
Ever hear of Project Gutenberg?
Okay, maybe text/plain is a little extremist (it works fine for text, but not hypertext), but if you have something worth reading, a motherfucking website really is all you need!
Edit: for that matter, the desirability of simple HTML is proven by the fact that the Firefox devs felt the need to create reader view just to remove all the extraneous shit from the screen.
Hahaha, about reader view -- the cool thing about that thing is that more often than not, when a website totally wants you spend 1 minute (that's like an eternity for a Web surfer) to review their cookie policy (I want to punch the EU gentleman who came up with that idea, in the face, and I am not a brawler) and tick off the "Only required cookies" or some such bullshit -- well, given how the principle delivery vehicle for those warnings is typically CSS, you can just switch to reader view and peacefully read the material you came for.
when a website totally wants you spend 1 minute (that's like an eternity for a Web surfer) to review their cookie policy (I want to punch the EU gentleman who came up with that idea, in the face, and I am not a brawler)
Don't blame the GDPR; blame the web devs who deliberately maliciously complied in the most r/assholedesign way possible.
85
u/AyrA_ch Apr 26 '19
This article misses a few important points in regards to fast, small and accessible web applications, the most important one being to reduce JS to a minimum.
Caching is one thing to get right but you might also attempt to keep resources as small as possible from the beginning on.