Re:Microsoft is building a Chromium browser to replace Edge ...
by Klonoar on Monday December 03, 2018 @10:12PM
(#18595790)
Mmmm isn't this effectively Gecko/Blink/WebKit now?
[ Parent
| on HN ]
Re:Microsoft is building a Chromium browser to replace Edge ...
by baroffoos on Monday December 03, 2018 @11:54PM
(#18596395)
Soon to be Servo
Re:Microsoft is building a Chromium browser to replace Edge ...
by ngokevin on Tuesday December 04, 2018 @01:18AM
(#18596825)
There’s not much work on a pure Servo browser beyond experiment. They’ve just various uplifted Servo bits like webrenderer and stylo into Gecko.
Re:Microsoft is building a Chromium browser to replace Edge ...
by Vinnl on Tuesday December 04, 2018 @03:31AM
(#18597502)
There's this which I'm hopeful for: Android Components [1]. If Mozilla make it easy for Android apps to use Servo as the shell for modern web apps, then the improved performance might make it worth it to "restrict" yourself to using only the features supported by Servo (i.e. without many of the workarounds that make old websites work).
Re:Microsoft is building a Chromium browser to replace Edge ...
by c-smile on Monday December 03, 2018 @10:14PM
(#18595815)
Blink and WebKit cannot be considered as separate implementations - their codebase is in sync AFAIK.
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?
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).