Tag: Charlie Owen
A ring of websites. A webring.
This may seem a bit bizarre to readers in 2019, but you’ve gotta remember that things were different back then. There were no search engines as they exist today. Google was still an academic side project at Stanford. Social media didn’t exist (oh my god the bliss). You couldn’t see what was trending, or see a retweet. There were no “278 friends are talking about this”. You relied on word of mouth for everything.
So webrings were ENORMOUSLY important for discovering new and exciting content back in the Age of Innocence. A 50 user per month site could find itself “next” to a 5 million visitor per month site, which would then start passing visitors to it. Hitting random would take you to things that you shared an interest in, but would never have any other way of discovering
We need to keep that beauty and weirdness going that first came with the early web.
Because the webs beauty comes from its diversity. A diversity of tech, and a diversity of people.
We’re the enablers and the defenders of that diversity.
So let’s not make it about us. Let’s make it about the wonderfulness of the Weird Wild Web.
Much of this is beyond me at this point in time. However, I wonder if WordPress is a part of this problem, rather than a solution? I was really interested in the discussion of Cutting the Mustard (CTM) and wonder what this might look like on my own site(s). At the very least I was left thinking that I probably don’t empathise enough.
The Web is incredible. It’s incredible because it’s stupid. It’s a collection of very stupid, or more accurately, very simple, technologies, all chained together to make something much greater.
We have got to the point where sites require ~2.5 megabytes to download, and the average content-based webpage is now bigger than a copy of Doom (a fully-fledged 3D shooter game) … Most of this size is due to sites not offering srcset variants on their images, and not taking the time to optimise images on those that they do offer. Some of it is due to third-party tracking, advertising, and marketing scripts (marketeers may well be the most script-heavy people in any organisation). A lot of it (but not most, by any means) is due to JS application bundles and third party scripts used to run a page (such as jQuery – still a major force on most of the web).
If we want to make the web better for people then the most important thing that we can do is to learn the basics. Not of technology, but of our fellow humans. Because, as we’ve show earlier, empathy is the most important skill that a developer can have. Our job is 100% about people, about our fellow humans. How can we do an amazing job for them if we don’t understand who we are building for?
So how do you combine 100% universality with the fact that some people have ancient, terrible browsers that it would be a time-sink to support? CTM gives the answer! Only those browsers that are “good enough” receive the advanced features. Those that have poor technology support silently fail the test and receive the core version. No having to support ancient browsers!
via Greg McVerry