Web development...

Web development. A long history, with many ups and downs.
Starting with simple HTML web pages, through sins of their time like jQuery and Bootstrap, to the first AJAX applications.
With the proliferation of REST APIs, separate architecture, and microservices, it finally seemed like we had found a reasonable
foundation on which clean and performant applications could be mapped to the web.
Unfortunately, this hope did not last long. Microsoft, the company that had given us VS Code and TypeScript, decided to take an absurd step. Instead of finally declaring Project Razor a failure as a lesson learned from the countless server-side rendered problem cases out there, they did the complete opposite.
They created Blazor. And with it, probably the biggest step backwards in developer history in a long time.
Blazor, just like its predecessor, is a crutch to allow backend developers to continue to "create" inperforming and half-finished applications using cheetsheets like Bootstrap.
The big news: the groundbreaking invention of WebAssembly is being abused to bring the COMPLETE dotNet runtime to the front end.
Not only is such a thing incredibly inperformant and energy consuming, now applications can be written in which C# code and JavaScript are written and executed in parallel. An absolutely unholy hell, not to mention the absolute unmaintainability of the code.
And they had actually, with the in dotNet 6 introduced minimal APIs, broken up and simplified the already somewhat outdated API system.
This little text was written out of pure dislike for this trend, I look forward to hearing your thoughts on the subject.
Your Josun