you are viewing a single comment's thread
view the rest of the comments
[–] 236 points 3 years ago (7 children)

Um actually... Opera and Edge weren't always based on chromium!

  • source
  • hideshow 14 child comments
  • [–] 105 points 3 years ago (3 children)

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

  • source
  • parent
  • hideshow 6 child comments
  • [–] 11 points 2 years 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.

  • source
  • parent
  • [–] 8 points 2 years ago (1 child)

    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...

  • source
  • parent
  • hideshow 2 child comments
  • [–] 17 points 2 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 19 points 2 years ago (1 child)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 12 points 2 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 2 years ago (1 child)

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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 28 points 3 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 22 points 2 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 2 years ago (2 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 2 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years 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.

  • source
  • parent
  • [–] 26 points 2 years ago (1 child)

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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 20 points 2 years ago (2 children)

    Can't you do that with any browser by changing the user agent?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 11 points 3 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 2 years ago (1 child)