all repos — gemini-redirect @ 95c9e4a2643a1484e2163d4b5b784e9ab590b905

blog/modern-web-bloat/index.html (view raw)

1<!DOCTYPE html><html lang=en><head><meta charset=utf-8><meta name=description content="BiRabittoh's official website"><meta name=viewport content="width=device-width, initial-scale=1.0, user-scalable=yes"><title> Modern web bloat | BiRabittoh's Blog </title><link rel=stylesheet href=/style.css><body><article><nav class=sections><ul class=left><li><a href=/>birabittoh's site</a><li><a href=/blog class=selected>blog</a></ul><div class=right><a href=https://github.com/Bi-Rabittoh><img src=/img/github.svg alt=github></a><a href=/blog/atom.xml><img src=/img/rss.svg alt=rss></a></div></nav><main><h1 class=title>Modern web bloat</h1><div class=time><p>2021-04-09</div><p>This is it. My first blog post; I guess I just became a boomer.<h2 id=inspiration>Inspiration</h2><p>Some time ago I stumbled upon <a href=https://odysee.com/@Luke:7/a-demonstration-of-modern-web-bloat:f>this video</a>, where the popular Linux influencer <a href=https://lukesmith.xyz>Luke Smith</a> talked about the effort of looking up a Chicken Parmesan recipe in 2021 without having any adblock or privacy extensions enabled.<p>I decided to build this website on <a href=https://www.getzola.org/><code>zola</code></a>, which is a modern engine for static sites! I was inspired by <a href=https://lonami.dev/>lonami</a> and I actually forked <a href=https://github.com/LonamiWebs/lonamiwebs.github.io>his code</a> to make <a href=https://github.com/Bi-Rabittoh/birabittoh.github.io>mine</a>. I think our websites are a good example of how clean and fast a webpage should be.<p>Yeah, this looks like a first world problem and it probably is, but it's not as subtle as you think. I'm actually convinced that the internet <em>could</em> actually benefit from this way of thinking, and that's what I'm going to talk about in this first article.<h2 id=the-problem>The problem</h2><p>In the early days of the internet, it was common for webpages to be written using only HTML, so we had very ugly but functional websites.<p>As technology went on, sites needed to get more modern-looking and <em>interactive</em>; that's why CSS and JavaScript were introduced into the mix, allowing for dynamic websites that could actually change based on user input.<p>As of nowadays, a lot more stuff went into the mix, to the point where the browser is now the most common program we use in our OS: you can, in fact, use it for doing things that 15+ years ago required external programs, like:<ul><li>playing music and video,<li>reading PDF files,<li>doing office work,<li>checking e-mail,<li>cloud storage,<li>etc...</ul><p>I guess people just find it more comfortable if they can do everything with a single program, and they're not to blame for that. This <em>is</em> the easiest approach for unexperienced people: just have a program that does everything, instead of having to learn how to use a bunch of different software.<p>This plethora of uses is possible today because of the existence of various libraries and frameworks that simplify JavaScript and CSS and make them easier to develop complicated websites with. This is good for basic web users who just want functional websites, and great for developers since they can easily code complicated code inside the browser, making it the perfect cross-platform wet dream we all have.<p>Sadly, this brings us to the problem: any modern website has become a burden for any browser to load, since our browser needs to download and parse through each library used and often fill the page contents as you scroll through. In his video, Luke Smith found that a simple Chicken Parmesan recipe would take up to 5-10 megabytes, which doesn't sound like a lot, but it actually is.<p>It's easier to understand it if you think about it with video-games; any game on 16-bit<sup class=footnote-reference><a href=#gaming-storage>1</a></sup> consoles and earlier, including full-fledged 30+ hour adventures like <em>Final Fantasy 6</em> and <em>Chrono Trigger</em>, weighs less than that one single recipe webpage.<h2 id=the-solution>The solution</h2><p>Well, I don't think this "problem" is getting solved soon, as new frameworks for web development are constantly being introduced. Sadly, it's a one-way train, but if you're a web-dev you could actually make a difference yourself!<p>I mean, this can not apply to all websites. Some of them just <em>NEED</em> to be as responsive and interactive as they are; most of them actually just became bloated at a certain time period (probably mid-2000s) when having a flashy website was cool and different from what everyone else had.<p>Nowadays you can be different than other websites by using plain HTML and CSS for your website: this ensures your pages will load instantly and be compatible even with the oldest of browsers!<p>If you like this philosophy, you can check out other projects that aim for a simpler and faster web, like these:<ul><li><a href=https://based.cooking/>based.cooking</a>, a modern recipe website based on collaboration via GitHub;<li><a href=https://wiby.me/>wiby.me</a>, a search engine that aims to only index classic style webpages.</ul><h2 id=footnotes>Footnotes</h2><div class=footnote-definition id=gaming-storage><sup class=footnote-definition-label>1</sup><p>As stated in <a href=https://blogs.umass.edu/Techbytes/2014/02/10/history-of-gaming-storage/#attachment_2827>this article</a>.</div></main><footer><div><p>Please use email for business inquiries <a href=mailto:andronacomarco@gmail.com><img src=/img/mail.svg alt=mail></a></div></footer></article><p class=abyss>owo what's this