• Shareni@programming.dev
    link
    fedilink
    arrow-up
    27
    arrow-down
    2
    ·
    23 days ago

    I mean the title should be “… time to move to the other browser”.

    Safari is the new IE with extra iCrap on top.

    Random browsers usually use one of the 3 web engines, but without browser polish, or functionalities like a working adblock. Those that don’t are just someone’s toys.

    So the only real option is Firefox, and the Mozilla foundation lost 80+% of their funding because they can’t get the Google money anymore. Maybe they’ll start actually funding FF instead of some BS humanitarian work that I can bet was primarily lining their pockets…

    • magguzu@lemmy.ml
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      edit-2
      19 days ago

      I wish Apple would open source Safari, or at least make some “Safarium” others can build on. Would be an instant third player without all the growing pains.

      • lengau@midwest.social
        link
        fedilink
        arrow-up
        14
        ·
        23 days ago

        The core of Safari (WebKit) is open source. If it weren’t they’d be violating the GPL license of KHTML.

        • magguzu@lemmy.ml
          link
          fedilink
          arrow-up
          3
          ·
          23 days ago

          Ah, admittedly I don’t know much. Could another browser build on it like Chromium or Firefox?

          • wvstolzing@lemmy.ml
            link
            fedilink
            arrow-up
            8
            ·
            23 days ago

            Smaller browsers built on webkit do exist; see ‘Epiphany’, ‘surf’, ‘luakit’, and ‘Nyxt’. Qt’s web component used to be based on webkit as well, though they’ve switched to Blink (Chromium).

            Unfortunately, none of the browsers listed above are 100% sufficient to replace Firefox. They all rely on GTK bindings on webkit, which has its own quirks; and none have support for webextensions.

          • lengau@midwest.social
            link
            fedilink
            arrow-up
            7
            ·
            23 days ago

            Yes! In fact, Chromium was originally a fork of WebKit, as WebKit was a fork of KHTML. In both cases the codebases have diverged quite significantly though.

      • Shareni@programming.dev
        link
        fedilink
        arrow-up
        3
        ·
        23 days ago

        I said they’re the new IE for a reason.

        The w3c standard: ok so we all agreed that this feature will be placed in the body tag

        Blink: ofc, that’s what I’ve been telling you

        Gecko: sure, idc

        WebKit: yeah nah, put it in the html

        So many little senseless gotchas like that that exist for no reason that to be iSpecial