At least there was a distinction between web of documents (WWW) and shipped apps with custom canvas. Rendering apps with web’s DOM is stupid. It makes websites a mess and relies on everyone using the same monoculture of browsers (like we now have Chromium, WebKit and Gecko, all nearly identical).

If browser does not support one feature (like CSS’s transform), the whole house of cards breaks. It’s like making ASCII art in notepad and then expecting everyone to use the same notepad app with the same font and style, to not break our art proportions.

We need to split web into websites and webapps, with webapps being browser dependent or full custom canvases and websites being immutable human-readable and editable format.

  • severien@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    If either of them had wanted to, they could have kept it close.

    I don’t know if you regularly work with large code bases, but that’s not true. It’s very easy to diverge significantly even if you don’t want to. That’s why there’s so much focus on short living branches, the long living branches cause a lot of pain.

    Now, if you have a hostile upstream, which intentionally tries to make that difficult - that’s a whole another story.

    We already have multiple browsers forking Chromium with the features they want and not the ones they don’t. Edge is this. Brave is this

    So, which core web platform features (things like HTML, CSS, JS, DOM, network stack, WebGL, WASM, File API, WebVR, WebXR…) Brave/Edge add or remove? Brave/Edge go with the first option outlined above, they’re more like shells (or skins if you will) around the largely untouched Blink.

    • Zagorath@aussie.zone
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      All the things you named are things that I think should largely be kept the same. Having them be identical or near enough to it is the goal I’m trying to achieve.

      Things that should be kept different are things like Manifest V2’s deprecation and WEI. Things that are, by their nature, comparatively surface level and separate.

      • severien@lemmy.world
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        edit-2
        1 year ago

        All the things you named are things that I think should largely be kept the same. Having them be identical or near enough to it is the goal I’m trying to achieve.

        So you just want to give Google total control over the core web platform technologies and other browsers will just accept what Google decided. That’s exactly the state I’d like to avoid.