3 ms·
Gecko ending embedding is almost certainly a major reason why everything built with a browser engine is either a Chromium wrapper (not true embedding, but no br
by kitsunesoba 5y ago
Gecko ending embedding is almost certainly a major reason why everything built with a browser engine is either a Chromium wrapper (not true embedding, but no browser chrome) and WebKit (true embedded).
It’s a real shame. Gecko is a nice engine but XUL is a much harder sell.
- cpmsmith 5y agoServo is the theoretical successor in this regard, like so many other regards, right?
- iFreilicht 5y agoIs the goal of Servo to replace Gecko eventually? I thought it was more of a testbed for new rendering techniques.
- classichasclass 5y agoCorrect. It's not intended as a Gecko replacement, and several important components in Servo are already part of Gecko. Servo will continue to evolve and new features will originate from it, but it lacks a lot of the legacy and quirks rendering (intentionally) that would be required to make it a full-fledged engine of its own even if Mozilla wanted it to be.