4 ms·

Mmmm isn't this effectively Gecko/Blink/WebKit now?

by Klonoar 8y ago

c-smile 8y ago
Blink and WebKit cannot be considered as separate implementations - their codebase is in sync AFAIK.
- saagarjha 8y ago
  Blink was forked a long time ago–do they still share patches?
  - fabrice_d 8y ago
    They share less and less. Blink did a `rm -rf third_party/Webkit` recently.
  - c-smile 8y ago
    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?
    - om2 8y ago
      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.
      - saagarjha 8y ago
        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-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 ago
    There 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 ago
  This made me giggle. Google and Apple are definitely developing their respective browser engines entirely separately.
baroffoos 8y ago
Soon to be Servo
- ngokevin 8y ago
  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.
  - Vinnl 8y ago
    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). [1] https://github.com/mozilla-mobile/android-components/ https://github.com/mozilla-mobile/android-components/

Mmmm isn't this effectively Gecko/Blink/WebKit now?

c-smile 8y ago

Blink and WebKit cannot be considered as separate implementations - their codebase is in sync AFAIK.

saagarjha 8y ago
Blink was forked a long time ago–do they still share patches?
- fabrice_d 8y ago
  They share less and less. Blink did a `rm -rf third_party/Webkit` recently.
- c-smile 8y ago
  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?
  - om2 8y ago
    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.
    - saagarjha 8y ago
      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-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 ago
  There 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 ago
This made me giggle. Google and Apple are definitely developing their respective browser engines entirely separately.

baroffoos 8y ago

Soon to be Servo

ngokevin 8y ago
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.
- Vinnl 8y ago
  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). [1] https://github.com/mozilla-mobile/android-components/ https://github.com/mozilla-mobile/android-components/