I don't quite get this... it sounds like the author mostly has issues with the HTML part of the web, but much of this seems to focus on the HTTP part.... why not keep http and just make a replacement for HTML? Writing an http server is very simple, too
Nope. And he has links to his blogs about what he doesn't like.
--- start quote ---
I used wget to download all 1,217 of the W3C specifications which have been published at the time of writing, of which web browsers need to implement a substantial subset in order to provide a modern web experience. I ran a word count on all of these specifications. How complex would you guess the web is?
The total word count of the W3C specification catalogue is 114 million words at the time of writing. If you added the combined word counts of the C11, C++17, UEFI, USB 3.2, and POSIX specifications, all 8,754 published RFCs, and the combined word counts of everything on Wikipedia’s list of longest novels, you would be 12 million words short of the W3C specifications.
I conclude that it is impossible to build a new web browser. The complexity of the web is obscene. The creation of a new web browser would be comparable in effort to the Apollo program or the Manhattan project.
It is impossible to:
- Implement the web correctly
- Implement the web securely
- Implement the web at all
Starting a bespoke browser engine with the intention of competing with Google or Mozilla is a fool’s errand.
--- end quote ---
https://drewdevault.com/2020/03/18/Reckless-limitless-scope....