What if we thought of browser engines less as monolithic entities and more as distros of the various libraries that comprise the Web platform?
-
-
I did not know that. Which bits?
-
Off the top of my head: Gecko uses Chromium’s IPC, WebKit’s regex JIT, and the Web Audio core shared by Chromium and WebKit. Also Skia, ANGLE, the OTF sanitizer, and the GLSL validator, which are sorta part of Chromium.
- 1 more reply
New conversation -
-
-
Yes, exactly this! And a ton of Servo/Rust components. I've been trying to find a good way to talk about / visualize how thinking about separate "engine" projects is double-counting things.
-
Some sort of visualization like "the size of the circle is the number of LOC" to show each of the libraries / major submodules; then with circles for Firefox / WebKit (various platforms) / Chrome / Servo for their dependency choices would be interesting.
End of conversation
New conversation -
-
-
What components from Chromium and WebKit? Safe browsing and the sandbox on GNU/Linux, right?
- End of conversation
New conversation -
-
-
wow really? TIL
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I meant from an end-user perspective, like a Linux package manager.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.