I can only think that modern front end development has failed

It's reductive to suggest that the top 100 represents "general culture" (whatever that ambiguous term means). There aren't solely niche musicians outside of the top 100. Theres plenty of musicians with millions of listens/views on streaming media that don't enter billboard lists that have extremely prodigious careers that have complex lyrics, use a wide assortment of instruments/equipments, evolve genres, etc.

Your data might be objective, but it's still a narrow slice of a much broader ecosystem.

In the end, everything is subjective, even morality. There's no objective physical law that says killing is bad. Animals do it all the time and could not care less about it.

But to the degree that we have a culture, though, we also have a non-100%-exact but nonetheless existing hierarchy of artistic works. There might be disagreements, even strong ones, but there's also some general agreement, that not everything is a fuzzy blob of equal value, left for the individual taste to sort or not, and this just for itself.

Is the idea that the Beatles are better than The Monkeys or Oasis, that Aphex Twin is better than Skrillex, that Dua Lipa is better than Justin Bieber, that Michael Jackson is better than Milli Vanilly, in some non-measurable but tangible way really that difficult?

That this, once a common and well accepted idea (related to the idea of the "canon"), appears like beyond the pale for the 21st century solipsistic individual, where only the subjective taste matters, is not really the fault of the idea itself.

I have a feeling that I am supposed to keep this a secret, but if you are tired of broken and slow websites, check out the Gemini protocol as a break from the BS.

It's not going to fix the web or replace it in a lot of cases, but it's nice to have an alternative for some things.

There are many reasons why having SPA and rendering your site on the client is a bad idea.

First, you are basically breaking the concept of the web, a collection of documents, not a collection of code that must be executed to get a document. That has many bad effects.

Browsing is slower, you have to download the code of the whole application and wait for it to execute other API calls to the server before the page is usable. That can take a couple of seconds, or even more on slower connections. With the old pages rendered server side not only you didn't have this effect, but also the browser could start to render the page even it was not fully received (since HTML can be parsed streamed). Not everyone has a fast connection available at all time, and it's frustrating when you have only a 2G network available and you cannot do basically anything on the modern internet.

It's less secure, since you are forcing the user to execute some code on its machine just to look at an article in a blog. And JavaScript engines in browsers are one of the most common source of exploits, given their complexity. Also JavaScript can access information that can fingerprint your browser to track you, without particular permissions. Ideally in a sane world most of the websites don't require JavaScript, and the browser would show you a popup to allow the website to execute code (just like they as you access to the camera).

It breaks any other tools that are not a browser. In the old days you could download with wget entire sites on your hard driver to consult them offline, with "modern" SPA is impossible. Of course that implies that it breaks things like the Wayback machine and thus history is not preserved. And serach engines penalizes sites that are not a clean static HTML.

It's also less accessible, since most SPA don't respect the semantic of HTML, everything is a div in a div in a div. And of course you still need a browser, while with HTML documents you could process them with any software (why a blind person need to render the page in a browser? While a screen reader could have simply parsed the HTML of the page without rendering it on screen...). It breaks navigation in browser, the back button no longer works as you expect, reloading a page could have strange effects, and so on. I can't reliably look at the address bar to know the page I'm in.

Finally it's less robust. SPA are a single point of failure. If anything goes wrong the whole site stops working. While a bug on a page on a classical server side rendered website breaks only that particular page. Also error handling is not present on most SPA, for example what happens if an HTTP request fails? Who knows. Look at submitting a form, most of the time there is no feedback. On a classical server side rendered application if I submit a form I either get a response from the server, or the browser informs me that request had failed and I can submit the form again.

It loads instantly on my Xr.