4 ms·
Blink and WebKit cannot be considered as separate implementations - their codebase is in sync AFAIK.
by c-smile 8y ago
Blink and WebKit cannot be considered as separate implementations - their codebase is in sync AFAIK.
- saagarjha 8y agoBlink was forked a long time ago–do they still share patches?
- fabrice_d 8y agoThey share less and less. Blink did a `rm -rf third_party/Webkit` recently.
- c-smile 8y agoPatches is not the only mechanism to keep code in sync. For two engines forked from the same source (same architecture and even same code tree structure) it is relatively easy to copy/paste feature implementation, no?
- om2 8y agoIn theory maybe, but in practice we rarely do. Sometimes even when the idea is pretty clear, like WebKit's CSS JIT, it's not that easy to copy because of underlying assumptions.
- saagarjha 8y agoJust curious, what kind of underlying assumptions are required for the CSS JIT (which is completely new to me! I had no idea this even existed)? I read this: https://webkit.org/blog/3271/webkit-css-selector-jit-compiler/ https://webkit.org/blog/3271/webkit-css-selector-jit-compile... but I didn't see anything specific (by the way, the spinning animation for the gear is broken on my Safari Technology Preview).
- alwillis 8y agoThere are enough similarities that Igalia (https://www.igalia.com/ https://www.igalia.com/) could implement CSS Grid for Blink and WebKit at about the same time.
- SimeVidas 8y agoThis made me giggle. Google and Apple are definitely developing their respective browser engines entirely separately.