Maybe we could tone down the #JavaScript / fuzzy notepad
▻https://eev.ee/blog/2016/03/06/maybe-we-could-tone-down-the-javascript
I’m having a really weird browser issue, where scripts on some pages just won’t run until about 20 seconds have passed.
Whatever you’re about to suggest, yes, I’ve thought of it, and no, it’s not the problem. I mention this not in the hope that someone will help me debug it, but because it’s made me acutely aware of a few… quirks… of frontend #Web #development.
Toujours faire du HTML+serveur classique qui marche toujours correctement, PUIS rajouter des fonctionnalités Javascript client pour ceux qui l’ont.
I’m not saying that genuine web apps like Google Maps shouldn’t exist — although even Google Maps had a script-free fallback for many years, until the current WebGL version! I’m saying that something has gone very wrong when basic features that already work in plain HTML suddenly no longer work without JavaScript. 40MB of JavaScript, in fact, according to about:memory — that’s live data, not download size. That might not sound like a lot (for a page dedicated to showing a 140-character message?), but it’s not uncommon for me to accumulate a dozen open Twitter tabs, and now I have half a gig dedicated solely to, at worst, 6KB of text.
#webperf #accessibilité #progressive_enhancement #amélioration_progressive #sémantique