Re:Microsoft is building a Chromium browser to replace Edge ...
by saagarjha on Monday December 03, 2018 @10:18PM
(#18595846)
Blink was forked a long time ago–do they still share patches?
[ Parent
| on HN ]
Re:Microsoft is building a Chromium browser to replace Edge ...
by alwillis on Monday December 03, 2018 @10:36PM
(#18595955)
There are enough similarities that Igalia (https://www.igalia.com/) could implement CSS Grid for Blink and WebKit at about the same time.
Re:Microsoft is building a Chromium browser to replace Edge ...
by fabrice_d on Monday December 03, 2018 @10:22PM
(#18595876)
They share less and less. Blink did a `rm -rf third_party/Webkit` recently.
Re:Microsoft is building a Chromium browser to replace Edge ...
by c-smile on Monday December 03, 2018 @10:30PM
(#18595908)
Patches 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?
Re:Microsoft is building a Chromium browser to replace Edge ...
by om2 on Tuesday December 04, 2018 @02:10AM
(#18597042)
In 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.
Re:Microsoft is building a Chromium browser to replace Edge ...
by saagarjha on Tuesday December 04, 2018 @03:36AM
(#18597535)
Just 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-compile... but I didn't see anything specific (by the way, the spinning animation for the gear is broken on my Safari Technology Preview).