3 ms·

Chrome is no longer webkit, and they have chosen to drop basically everything not directly applicable to chrome in blink.

• laumars 12y ago
  To be honest you're just arguing semantics as Blink is a fork of the same webkit components that Chrome was using previously. So little has changed from a rendering perspective. Given the amount of redundant code in webkit due to Google and Apple pushing the library in slightly different directions, it does make some sense to fork it. And it's really no different to Apple forking webkit themselves (webkit2). However when the forks diverge more in the future, your point will be more relevant (just as the difference between kHTML and webkit is now quite pronounced). In any case, I did reference Blink in my first post. So your point isn't lost on me :)
  • icantthinkofone 12y ago
    "Blink is a fork of the same webkit components that Chrome was using previously. So little has changed from a rendering perspective." Nothing could be further from the truth.
    • laumars 12y ago
      [Citation needed] But seriously, simply stating someone is wrong is less constructive than not replying at all. I'm open to correction :)