>>3506
>And it was also very stable despite the "cartoonish" (at the time) look, since it was built on the rock solid Windows 2000
This. Much as with OSuX, XP switching end-users to a buzzword-compliant modern kernel from NT and introducing new GUI architectures to eliminate desktop tearing/flicker/stutter/priority in ways loonicks is still struggling to with Wayland is laudable, even if there were some sacrifices made and superior alternatives ignored.
>>6269
>Badwolf is
Yet another KHTML-knockoff frontend alongside Chrome & Safari, further cementing the standards-destroying browser engine monoculture that only Firefox/Palememe now fights against
>>6276
>The question is what do you want from your browser?
QFT
>Right now the goal is to tack on every feature that a full operating system has, and then some.
I think the really scary flaw is slightly different: Right now the goal isn't just to tack on an OS, but to keep piling complete OSs inside complete OSs forever in concentric layers.
>>6277
>I've been evaluating Java, or possibly Python with the performance-critical parts ported to Cython, as a platform to build a browser upon.
LOL case in point
Serious talk: While it's easy to rag on browsers themselves, because they totally DO SUCK (and always have,) and could trivially be MUCH better if brought to the standard of quality for practically any other type of software, are they really the source of that much badness in practice, by themselves?
Take a modern ChromeFariFox browser, and load up a svelte sane XHTML+CSS page, semantically marked up for alternate or fallback CSS, and no or minimal JS as appropriate to its purpose. It's not perfect, but it's reasonably fast, stable, pretty, and usable.
FAR AND AWAY the biggest problem with the modern web isn't modern bloated browsers, nor modern bloated WHATWG "living standards", nor as >>6279 suggests the centralized brittle topology of TCP/IP, nor even the consoomerized walled garden botnet bloat phones/tablets normalfags use to access it. Those are all problems, and fixing them would be good, but the misery of using the modern web would not noticably improve.
The web's problem is quite simply THE WEB ITSELF
I'm not sure how that could ever be fixed, aside from encouraging people to write webpages less app-like, and code apps less web-like, sadly the fact so many nudevs are unfamiliar with any toolchain other than webshit means exactly the opposite is happening.
That said, if I were to spitball a tentative solution, I think about 90% of the problem could be solved by the creation of a protocol for Db CRUD GUIs amenable to native clients, which encompasses all or nearly all the functionality of the most noisome "webpages that shouldn't be webpages"/"apps that shouldn't be apps".