The Web I Want (2018)
quii.dev
The Web I Want (2018)
1–10 of 70 posts
Re: The Web I Want (2018)
#2Interesting thought experiment: aside from streaming videos, how much bandwidth do you actually need a day? That's updates, posts, tweets, news articles, and so forth.
Not very much. It's not unusual to load a humongous site with tons of libraries to get one or two sentences of information you wanted, usually after the obligatory 3 paragraphs of bullshit AI text.
My guess is that the actual information, in text, that you consume in various forms is extremely small. The ratio keeps getting worse and worse for the consumer.
Re: The Web I Want (2018)
#3This website says it better:
Re: The Web I Want (2018)
#4> Most websites are about delivering and exploring content. HTML is amazing for this, and you don't need JavaScript.
Most commercial websites want analytics on how users browse and click on the website. So this point goes out the window.
Re: The Web I Want (2018)
#5> Most websites are about delivering and exploring content. HTML is amazing for this, and you don't need JavaScript. Most commercial websites want analytics on how users browse and click on the website. So this point goes out the window.
This is why the web (and computing in general) is the way it is today: everything prioritizes what businesses and developers want, and the desires/needs of the people who actually use it are considered afterthoughts and annoying inconveniences. :-(
Re: The Web I Want (2018)
#6[flagged]
Re: The Web I Want (2018)
#7Interesting thought experiment: aside from streaming videos, how much bandwidth do you actually need a day? That's updates, posts, tweets, news articles, and so forth. Not very much. It's not unusual to load a humongous site with tons of libraries to get one or two sentences of information you wanted, usually after the obligatory 3 paragraphs of bullshit AI text. My guess is that the actual information, in text, that…
Agreed. Everyone nowadays wants to make their media in non-text forms like videos, when I would honestly prefer that your tutorial on how to bake cookies could just be in text form. We shouldn't have to load megabytes of JavaScript to "watch" a recipe online that could easily be done in writing.
Re: The Web I Want (2018)
#8I've ublock installed with the advanced user setting ticked, JavaScript disabled by default. The amount of blogs that load nothing until JavaScript is enabled is ridiculous. And some sites simply don't run unless you enable 60 odd 3rd party JS scripts to run.
Either way my experience of the web is fast and generally fine and any site that wants me to jump through hoops in ublock to run I don't bother with and I'm happier for it.
Re: The Web I Want (2018)
#9Frameworks are a form of lock-in, or a moat. Once you build something complex, the cost of your customer changing supplier is higher. You build that local pub website using big fancy stuff and they can't hire a WordPress person to do some simple updates. Never mind a plain HTML and CSS person.
Sure, it's easier for whomever built it, but it's also harder for anyone else. You are using these tools and frameworks to serve yourself, not your customers.
It's like using VB to customize MS office, or the total lock-in you face with SAP customizations. But in those cases it maybe brings some value. With web sites you're really building complexity without improving presentation or adding value.
Re: The Web I Want (2018)
#10> Most websites are about delivering and exploring content. HTML is amazing for this, and you don't need JavaScript. Most commercial websites want analytics on how users browse and click on the website. So this point goes out the window.
Also, I’m not sure that most websites are about delivering and exploring content. I think most websites are fundamentally about either delivering ads or selling you stuff. “Delivering ads” usually requires JavaScript, and “Selling stuff” can be done without a bunch of JavaScript, but the experience wouldn’t be great.
I don’t dispute the thesis of “web pages today are often way too bloated”, but I think it’s important to be realistic about the problem space. The author calls out JavaScript driven carousels as an example of unnecessary bloat… yet the Amazon.com home page features one such carousel prominently. I doubt they would put it there without A/B testing the heck out of it. To be fair, Amazon is way smarter about it than most in how the page paints and is interactive very quickly, but my point is that it seems to me that most web users want something more than what JavaScript-less HTML and CSS can provide.