Not sure Tim Berners-Lee’s vision was to have 148 requests transfer 5.3 MB of assets to deliver 15 KB of text
Not sure Tim Berners-Lee’s vision was to have 148 requests transfer 5.3 MB of assets to deliver 15 KB of text 49 comments
@rvedotrc in this case, they’re made-up numbers to express an experience [https://mastodon.social/@urlyman/112965031272068593], but in the general vicinity of https://tonsky.me/blog/js-bloat/ @macronencer it’s what happens continually in an economics that does not care about what it externalises. But it will care. Eventually highly related: https://en.wikipedia.org/wiki/Jevons_paradox tldr: @macronencer @urlyman “Wait, it has even more horsepower? Can’t stable them ponies!” J'ai mieux compris quand je suis arrivé en Bosnie-Herzégovine, et que ça m'a coûté 60€ pour afficher l'adresse de mon Airbnb 😱 (à 7,5€/Mo) @urlyman @urlyman I got my career start in the Web 1.0 server-side Java world but had the opportunity to do some work with a couple former DataPoint guys who invented ArcNet. We had some great conversations about how expectations about available resources and approaches to optimization have evolved over time. We all agreed that no web page should ever have more code embedded in it than the original UNIX source code base But here we are... @m0xee can you expand? I’m not well-versed on networking protocols ( I’m more of a front-end bloke) @urlyman @unsaturated @unsaturated @urlyman there's me, earlier in the year writing the page for my weather station so it shows graphically the current status with real time live updates & got it all to be about 64k in total. At some point I'll try to cut that by a few more k as there's some white space that's not needed. The development page: https://weather.area51.dev/dash/home @urlyman If a website doesn't work in Lynx over a 56K dialup connection, then it simply doesn't work. #ProgressiveEnhancement or GTFO. @midzer @urlyman which is what @urlyman "If present trends continue, there is the real chance that articles warning about page bloat could exceed 5 megabytes in size by 2020" https://idlewords.com/talks/website_obesity.htm @urlyman okay, a nice 15kb text article, and a nice 1MB photo or two. none of this JS waste and ad-gunk. ...and disable basic browser navigation with half-assed javascript intercepting the user's clicks, then blame the end user for being backwards when the end user complains about this. @urlyman @jwildeboer while in the mean time consuming an inordinate amount of resources on your local computer… |
…putting the ‘ass’ into assets