• hector@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    7
    ·
    9 hours ago

    The problem with Web Standards is that they’re so complete, broad and complex that it’s very hard as an independent team to get started writing a browser.

    You’d have so little daily active users compared to the titans products (Chromium, Gecko, WebKit) that even if you made something super good, it would still be hard to guarantee website compatibility without faking the user-agents.

    There’s also a lot of complexity involved in writing a sandbox for every instance of a website (tabs or iframe) and sharing information between multiple process. I don’t know how they do it in Chrome, but in Firefox they have a whole specification language for that which compiles to C++.

    You also have to recreate the DevTools and other tooling for developers to adopt your browser and for you to debug any issues with your DOM renderer…

    I love how much the web has to offer nowadays with technologies like WebRTC, WebSocket, Blobs, GamePad API, modern CSS3 but it has also the effect of locking us down into a tiny ecosystem.

    I really their should be legislation on what companies can do with their browser because they’ve become such an important piece of the internet so they should serve public good.

    I don’t know how to make it happen and I don’t even know if it’s a good idea when you consider the governance issues it would bring for open-source project.

    I’m really passionate about this technology !