• LeTak
      link
      fedilink
      English
      1031 year ago

      Chrome was not always based on chromeium. Chrome was based on Apple WebKit until 2013 when they forked WebKit and made the Blink engine.

      • @Dapado
        link
        431 year ago

        Chromium was still the base before the WebKit/Blink fork. Chrome and Chromium were released simultaneously in 2008.

      • @[email protected]
        link
        fedilink
        11
        edit-2
        1 year ago

        Chromium has always existed. Originally it was wrapping web kit and later they forked web kit into blink and diverged from Web kit. Chromium is a level above the engine.

      • ElPussyKangaroo
        link
        81 year ago

        Wha- hold up… I’m not sure I understand…

        Chrome was based on WebKit?

        I’m not aware about the old stuff as much so if someone could fill me in…

        • @Dapado
          link
          181 year ago

          WebKit is a rendering engine which is one of the major components of a web browser. Chrome/Chromium was released in 2008 using a modified version of WebKit as its rendering engine. Eventually in 2013 they created a fork of WebKit called Blink, which is the current rendering engine for Chrome/Chromium.

          • exu
            link
            fedilink
            English
            181 year ago

            In more history, WebKit is a fork of KHTML. That’s the reason why WebKit itself is open source.

            Apparently there hasn’t been active maintenance since 2016 though and it’s officially dead since this year. RIP

            https://en.m.wikipedia.org/wiki/KHTML

            • @[email protected]
              link
              fedilink
              121 year ago

              Remember Konqueror? That’s KDE’s web browser, which still uses KHTML. I should try it out again and see how it’s held up.

              • @Phrodo_00
                link
                31 year ago

                I’m not sure, but didn’t Konqueror switch to qtwebkit at some point? Or was that a different qt-based browser?

                • @clubb
                  link
                  11 year ago

                  I think thats falkon

          • ElPussyKangaroo
            link
            21 year ago

            I see… Interesting.

            Does anyone remember Microsoft Edge’s original engine? Was that an original base or also a fork of something?

    • @[email protected]
      link
      fedilink
      271 year ago

      Pre-Chromium Edge wasn’t even that bad. Sure, the engine had its issues and there was probably a bit of Edge-specific JS on some websites, but I’m sure they would’ve eventually got there.

      But seeing that even Microsoft abandoned making their own browser engine, it goes to show how complex it is to make one nowadays and with new web APIs/features coming out every few weeks it feels like, it’s almost impossible to keep up.

      • TAG
        link
        221 year ago

        But seeing that even Microsoft abandoned making their own browser engine, it goes to show how complex it is to make one nowadays and with new web APIs/features coming out every few weeks it feels like, it’s almost impossible to keep up.

        No, Microsoft is just historically bad at making browsers. It was not until Internet Explorer 7 that they finally implemented HTML 4 and CSS 2 without major glaring bugs.

        • @Aux
          link
          81 year ago

          Microsoft was never bad at making browsers, their issue is that they tied browser release to Windows release cycle. IE6 was the best and the most compatible browser on the market in its release date. But it didn’t get a single update during its long life. 5 years old Chrome is completely useless today even if it was a pinnacle back then.

          • TAG
            link
            11 year ago

            Sure, but Windows Update was already part of the OS and web users were a customer segment that had an Internet connection. They could have pushed patches and bug fixes.

            • @Aux
              link
              11 year ago

              That’s not Microsoft philosophy. Microsoft has strong backwards compatibility. If they would change how border box is rendered on the screen, that would break a lot of apps which use IE engine as a web view. Thus they only push security updates, but ensure that rendering stays the same within one Windows version.

            • @Aux
              link
              11 year ago

              To existing web standards at the time.

    • TWeaK
      link
      fedilink
      English
      261 year ago

      Opera was the shit back in the early days. It could pretend to be any other browser.

    • Espi
      link
      fedilink
      111 year ago

      I have an installer for Opera 12.18, the last one to use their Presto engine. Every once in a while I test it out to see how it has aged.

      It’s not pretty haha. It barely works.

    • @nexguy
      link
      101 year ago

      Always weren’t been