Switch to Svelte. You’ll never look back. Everything else is trash.

Naah, I do not have imaginary conversation. Those are what many people I speak on some discord server actually say when they talk about the web being too complex. While they used discord. And many people at that. That's why I jump to the assumptions, my bad then.

I am not who you think I am. I also never said half of that. You seem like the type who likes to gaslight and imagine conversations.

I assume you are one of those people that wants the web to go back to the 2000 era. Where JS is not as wide spread and multimedia is expensive to load. That's why I assume if you want the web to be simpler you advocate for removing many of the current web standards/API. I meet too many people like that hence my immediate assumption

The caching and boot time scenario is very compelling, for teams who have an actual web APP to deploy, not just a web SITE, but... why were they not just leveraging the caching capabilities the browser ALREADY has?

Like, genuine question: what caching capabilities does a Service Worker that the browser doesn't already do?

That doesn’t need to be the case. Yes, there is a place for a “web app” with advanced tech, but most of the web isn’t a web app.

And, regarding native apps, that’s why there are downloadable web apps made in Wails, Tauri, or that disgusting Electron.

The alternative to a less complex web is we will have more native applications. And honestly, I do not prefer that

Oh I've set up a PWA with that before! It really is wonderful to use! (although my service workers are only an image caching layer for now as I need my data to stay fairly in sync with my db)

More people needs to know about Vite PWA project. It will generate the service worker for you and still provide the escape hatch if you ever need to write it your own too!

Because they add another layer that can make something more complex.

The better question is: how can we make something less complex?

While it’s not my preference, there’s a huge benefit to a basic LAMP stack with no JavaScript.

Ego

I am still confounded by the fact that to "be standard.site" you have to put extra data on a PDS. And this is done just so links get nice embed cards on Bluesky?

To give my normal "standard web" website a nice embed on Bluesky I have to add each and every article on Bluesky?

How does this make sense? Why is this desirable over data that's entirely in the page itself? What am I missing?!

nice, AT getting some love in fediverse :]

The RSS 2.0 specification is copyrighted by Harvard University and is frozen. No significant changes can be made (although the specification is under a Creative Commons licence) and it is intended that future work be done under a different name; Atom is one example of such work.

i had it completely wrong the whole time, i actually thought Atom was kind of a fork from the frozen RSS 2.0. That it had the same structure, just with more fields - to put it simply, RSS 2.0 with more features.

They are totally different format: different structure, different keyword, different time date format, different escape way, different language specifying way...
Their common parts are only both used for feed and both use XML.
And even more, interoperability of RSS 2.0 itself is horrible, RSS 2.0 standard left too many details in not specified situation, such as how to deal with relative URL...
For more infomation, you can read https://www.intertwingly.net/wiki/pie/Rss20AndAtom10Compared

Are RSS and Atom not supposed to be interchangeable?

Tbh, i never really paid attention which one i was subscribing to, it always worked.

Unfortunately, IIRC, some feed readers only support RSS, not Atom. Those users may see some warning like "invalid format".

HTML5 is a beast of a spec. Like, if properly used it is enough to make a functional UI with modal and tooltips and whatnot. This is what makes it popular for not just "web" application IMHO because you then no longer need to learn yet another DSL for UI (electron, react native, capacitor js, expo)

Table of Contents

1.    Find your bottleneck first
2.    Slow server response time (TTFB)
3.    Render-blocking JavaScript and CSS
4.    Large image and video files
5.    Third-party scripts
6.    Slow interactions and a blocked main thread
7.    Unoptimised JavaScript
8.    Unoptimised CSS
9.    Web fonts
10.    Plugins, themes, and page builders
11.    Aggressive bot and AI crawler traffic
12.    Make speed a team habit

So, first step is selling the product. Second step, check if the server is actually working fine.

Steps 3 - 11 -> fix your fucked up shit

The fix for 5 is REMOVE THAT FUCKING SHIT. Very similar fix for 10

I skimmed the article and they just say:

• Don't roll your own page scrolling.
• Don't roll your own link navigation.
• Don't roll your own text selection.
• Don't roll your own context menu.
• Don't roll your own copy and paste.
• Don't roll your own password field.
• Don't roll your own date picker.

For a date picker I initially disagreed but then their argument about how you can just use 2x input type=date for the start and end date and then it's consistent across every site was pretty reasonable. I'm not gonna go read mdn on its capabilities right now so maybe there's still some valid use cases for not using one, like conveying to the use what valid ranges they can select.

But yes I agree you shouldn't use a library for something simple like left-pad

Is it ad blockers, reader mode and turning off JavaScript?

The alternative of using someone else's framework for every single basic function is equally bad.

It needs to be balanced.

Before publishing, that text really needed a self-review/read-through. So many obvious issues to spot. Numerous typos like 'techjnical ', issues like double words 'missing missing', and so on.

No, there's a clear distinction between a native application and a website. I could go on and on about my hate for native app and it's difficulty to develop for more than one platform, but the point is only SOME apps needs to be native IMHO. Apps like CAD, multimedia editor and player, server application, and developer toolchain. Something like instant messaging, video conference, multimedia streaming, forum can be a web app.

it's definitely what google was going for