I think we are increasingly needing a stronger separation between functionality oriented applications that operate in the browser vs media-based content (documents/videos/images/articles).
The web has become an unnecessary-hostile platform for web applications because you are standing on a thin layer of glass the whole time because you have to juggle so many combinations of environments and browsers and capabilities and devices and screen sizes and internet speeds and everything in between.
For example there's an insane amount of baggage involved today in deploying a decent production web application in terms of bundling the assets caching vendor prefixing feature detection and so on..
So much of that could go away if we had a more application-focused platform on the web.
So someone could say you want a web-based customer service desk application? Here install this 30MB bundle once and let us focus on everything else. It's not a big ask.
Instead we have a mindfuck of "minifying" "vendor prefixing" "css autopefix" "css sprite" "code splitting" "tree shaking" "___ javascript library that is only 4 kilo bytes!" "hash based cache busting strategy" "feature detection" and so on.
It just adds unnecessary complexity and baggage.
As a long-time web dev I'd like to see the web platform for applications evolve into a more friendly and predictable environment for the developers more similar to the mobile app platform.
That was basically Java applets, and then later JNLP and Flash.
It turns out it is a big ask. Users really don't want to install software, and their attention span is literally about two seconds. Javascript + DOM "won" over Java applets for two main reasons: you could access the whole browser window, and you could display something on the screen immediately without needing to load your whole application's functionality.
We didn't like JS back in 2002 either - the Java ecosystem was much more mature and easier to program with. But we put up with it because users expressed a very clear preference for DHTML apps over Java applets, and money follows users, and devs follow the money.
All the tree-shaking, code-splitting, minifying, etc. is there to preserve this "loads quickly" property as JS apps have gotten more complex. A lot of sites do it poorly, but think of those sites as prey for an enterprising startup willing to put the extra effort into snappiness.
The method that we have makes sense for frequent hopping between different documents on different sites and spending some minutes on each. As was the case with the original "web of linked documents".
But now there's undue baggage and pressure and complexity imposed on application developers because on one hand they are developing sophisticated applications that people use daily for many hours.
On the other hand they have to worry about the most trivial things like if some library of bundle file is 200KB or 1MB.
Or worry if javascript is even enabled or not, if whatever CSS feature like flexbox or grids or whatever is supported or not.
A trivial thing turns into something complicated because you need fallbacks and polyfills and fallback for your fallback and you know the rest. It hurts the developers but also the users because time and effort that could be spent on the product is spent on this kind of stuff.
That's why I think the separation of content and application is becoming more important.
If you want snappy media that is not bloated and responsive and readable and open and all that fine.
But if you want a full-blown CRM or spreadsheet or customer support desk software and the like that you spend your day on let's give the developers a break and give them a predictable environment with a robust method of application delivery, without bean counting the bytes, and empower them to focus on the real problem that they are trying to solve for you.
Should desktop/laptops be the same? Is it only because desktops/laptops started long before the internet was fast enough to support that apps that they don't run like phones/tablets?
I don't want a locked down desktop/laptop. I'm only pointing that that more people than own desktop/laptops are constantly downloading and installing 30M bundles
I can think of at least two instances in the last week where I've had a desire for the functionality offered by a big-name product (Groupon and Zillow), went to their mobile website, was confronted with a nearly-nonfunctional mess and a prompt to download their app, and then said, "Eh, I don't care enough to bother and wait for it to download."
In so far as your web app really is something that should be a full scale app (google maps being the classic example) this is a great trick. But as an industry, we have incentive to shove complex apps down people's throats when the use case requires plain-old-media with just a bit of dynamic stuff for navigation and forms.
I prefer web apps because when I go to a bar and want to order from my table, or want to see the schedule for a conference I'm attending, I don't want to go to the trouble of installing a new app for something I'm only going to use once. This used to be a lot worse when apps asked for a load of permissions upfront which it wouldn't be sensible to grant, but these apps still often take up around 100mb in storage, which can mean having to find something to uninstall if you have limited space.
That's a pretty horrid mischaracterization. Users may download and install apps that are tens of megabytes per bundle, but at least the downloaded blob is then entirely local. The apps don't redownload themselves on every startup.
Let's compare that to a bloated megalith webpage with framework machinery, a dozen trackers and $deity knows what else. "ETag has changed, please wait while we drip feed you this >20MB JS+CSS gob. Oh, and btw - you can't see the page text at all until the download has been processed."
Yuck.
We already have that platform, the desktop. Sure the distribution side of things could be improved, but there is nothing wrong with the platform.
Here's the thing - people don't like to bring in a more complex technology simply to do exactly the same thing as they could do with a simpler one. They need to justify its presence in there somehow.
For instance, supposed you decided to re-implement hacker news with a client heavy javascript framework. Would you leave it looking exactly the same as before? Almost certainly not, you'd start using that javascript stuff, and (in my opinion), the end result would no longer be the simple, easy to read, text based website that it currently is.
That's the connection I'm getting at here (and once again, it's something I'm mulling over, not a hard conclusion I've reached).
It's rarely the case that you change design because you selected a new technology; rather you usually select a new technology to enable changes in design.
If I switched from React to Vue for a Hacker News viewer I'm not also going to change the design of the project just because. But if I wanted a dashboard to become dynamic and allow for smoother user experiences without a full page refresh each time chances are I'm going to introduce JavaScript to a page that was previously just HTML and CSS.
Take this block of text in the article:
"I thought my eyesight was beginning to go. It turns out, I’m suffering from design."
Instead of leaving it a legible black and have the divider + italics convey the separation from the article...
They went with rgba(0,0,0,0.5) on a font that is hard to read on a white background with that shade of a gray. Try removing those sort of CSS rules from the Wired Article and you'll find it much more legible.
They repeat this sin whenever they quote someone such as:
A color is a color isn’t a color… …not to computers…and not to the human eye.
They also put a ton of whitespace around the quote which is already enough to separate it. The absurdly annoying light gray is annoying and not required.
One thing I notice in my work (in product management) is that people naturally gravitate towards shiny things. So we design things to be shiny in order to attract those people.
At various points, a specific aesthetic gains popularity because, for well-founded reasons, it increases usability and readability. Then everyone starts to imitate it, partly because it works, but also partly because people are drawn to it. Then frameworks are created to enable teams to rapidly replicate the style.
At a certain point, the frameworks are good enough to just replicate the style in basic settings with little input needed from someone who is actually thinking really hard about the design. In many ways that's a good thing because it lowers the barrier to entry. It's much easier to make things because the framework drastically reduces the amount of wheel reinventing you'd need to do. But you end up with designs where nobody really thought that hard about it - and so you end up proliferating potentially bad defaults encoded in the frameworks.
I'm personally much more willing to believe that the decline in overall design quality is due to negligence from convenience.
The web as a publishing platform shouldn't need React or 2MB of js libraries
Web apps are a different story but have also different requirements
I've been mostly a web developer for the past 20 years and I can't understand why there isn't a good solution yet
Look at 4chan or Craigslist
They're highly successful and they serve pure static (ugly) html
I think the reason is simpler, more like fashion: most people who are in a position to play with fonts and colors have absolutely no idea what they are doing and make decisions by copying somebody else who they perceive as cool, and there is always pressure to make it look cool, so it spreads.
To be clear, the article is almost solely about contrast between text and background colors, not JS heavy frontends. But I think what you've stated is very true and is also my opinion about the current state of web frontend.
Like another user said here, the contrast is a result of designers working with a page with too much content, and trying to reduce the feeling of content overwhelm. I don't think heavy JS frontend is directly related to that. But what you've said should not be discounted.
To be clear, this is something I'm mulling over, not a hard conclusion, but here it goes...
Creating a simple, server rendered, text based web site may be exactly what the users need, but from a developer's point of view, it can also be a career risk. A rapidly increasing percentage of development jobs out there now require experience with a front-end framework. As a result, developers need this experience, so they start adding front end frameworks in order to 1) gain that experience, and 2) document that experience in a real world project. Remember, a project isn't just a project, it's an audition for your next project. This is how tech recruiting works[1]. So developers may be adding new bells and whistles that are not only unnecessary[2], but actively harmful to their current project, largely because they are necessary to their resume, and it's actively harmful not to have them there.
In short, one of the reasons the web is becoming unreadable is that web developers can't create the resume they'll need for their next gig by using the best tech for their current one.
[1] I'm getting long in the tooth enough to have seen this a few times. Companies required "EJB", it wasn't enough to have experience with Tomcat and standard Java. Later, Spring, Struts, Hibernate, iBatis were required. These days, it's ember, react, and other rapidly evolving JS frameworks.
[2] I want to be clear that I think many of these frameworks are actually pretty excellent, for projects that need them. The problem is, if your current project doesn't, you still have a strong incentive to bring them in.