It’s wild to me I still see people say that Safari and Chrome are the same rendering engine. The Blink fork happened over a decade ago, they’ve drifted a ton since then.
It’s wild to me I still see people say that Safari and Chrome are the same rendering engine. The Blink fork happened over a decade ago, they’ve drifted a ton since then. 19 comments
@misty Interesting, I know next to nothing about Apple, so I always just kind of took people's word when they said that. Thanks good to know a little about the history. @misty I still mentally classify them as KHTML-based browsers, but I realize that’s even more out of date. @misty I'm guilty of this, too, but in my defense, the last ten years have been A Time. @misty And that's the second fork. The original Chromium was based on a fork, then they got it merged upstream but there was still a lot that was just conditionally compiled so that there were some features only used by Chrome (for instance, it had an entirely different JavaScript engine) and some used only by the other WebKit ports. After a while where they were maintained in one codebase but with a lot of ifdefs and divergence and conflict, they eventually forked again. |
@misty Genuinely had to inform someone of this recently. I was like, there have been multiple real world coups and many jumps in global warming since the two forked. Multiple US presidents, as well.