[easyThrowaway]

He's missing the last step:

Somehow around the 2010s we all decided that everything in the web had to become "reactive" and "asynchronous" - which is a fancy way of saying things can theoretically happen at any time but realistically if you try to make it happen in ways that don't resemble the previous serial approach you get weird race conditions - and instead of making sure this was implemented in HTML now we have to write another web browser on top of our web browser in javascript, using a thing called shadow DOM.

Also somehow now you have to understand how the internet works at protocol level unless you want way worse performance than that page written in Dreamweaver 20 years ago.

But this is fine because this is the way big companies run things, which we all know they always make the correct decisions like giving their AI full access to their login and password recovery process.

[pllbnk]

I have been building a small web app for my family recently. I was planning to host it on my own server and not do any fancy reactive and asynchronous stuff. It was a simple multi-page app with simple forms and links. And it sucked because we didn’t know who was doing what live, we needed to refresh pages needlessly just to see if something has changed. Funny that it seemed fine while I have been the only user testing the app but once we got more family members in what seemed like “production ready” it was immediately obvious that it needed interactivity.