• drwankingstein@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    16 days ago

    I don’t think it would be that bad. Users have proven willing to eat whatever trash chrome shoves down their throat. Firefox has also proven that they don’t really do a great job at preventing chrome from controlling the web market as shown with JXL. They completely dropped the ball here and only recently after safari has proven to successfully adopt it, choosen to follow suite.

    Apple has turned out to “prevent the chrome monopoly” far more effectively then firefox has.

    • leetnewb@beehaw.org
      link
      fedilink
      arrow-up
      16
      ·
      16 days ago

      Apple has turned out to “prevent the chrome monopoly” far more effectively then firefox has.

      Turns out that owning the platform (Android, iOS) counts for a lot. I like having an independent option.

      • Midnitte@beehaw.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        15 days ago

        It probably helps that WebKit was forked from KDE’s Konqueror/KHTML and that Blink was a fork of WebKit.

        Compared to Gecko, I’m sure they behave the same as far as webdevs were concerned - hindering it’s adoption - webdevs don’t want to support esoteric engines for obvious reasons.

        • drwankingstein@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          15 days ago

          webkit and blink are two massively different beasts, webkit and blink is just an engine in the end, the stuff on top matters too. If it was as simple as engines, it would be like comparing gnome web to chromium.