It does, it makes sense. These standards led us to everything that has ruined the old web, it led us to corporate controlled Internet where few major websites aggregate 80% of the content. It led us to scroll-jacking, bot-driven, located behind firewalls and captchas websites where genuine users can't even log in or post anything. It is why we have to use browsers that are more complex than entire operating systems just to support everything that can be done over HTTP. It led us to monopolies on web browsing - how many pages of web standards you have to implement and comply with if you want to make your own browser, just to visit google dot com? And at any time and moment all your efforts can be interrupted by security researchers who would tell you that your browser is insecure and now you have to comply with hundreds of pages of security standards as well, all because of how much can be done over HTTP. You can't even host a simple website over just HTTP without somebody telling you that you have to use HTTPS, even if you don't need it, because why not? You'll have the green icon!
And because of such monopolies, most websites also turned into "shells" that try to ruin your experience as much as possible so you go and download their app where they have more control without being restricted by browsers. And this, in turn, led most people going off the general web and staying inside their apps.
Sure, you can make your app that throws away most of HTTP-based bloat, but then someone forks and makes it support some of the bloat because they like it that way, and then someone else adds a bit more, and we are back at it again. You can't just "go back" and strip everything from HTTP, entire thing has to be done in entirely different way where there is no possibility of repeating history, because there is no other road history of HTTP can walk by.