5 ms·
I always wondered why the engine is not separated from the GUI in browsers. In chess world this is totally normal, you have a chess GUI and a chess engine (and
by nilslindemann 5y ago
I always wondered why the engine is not separated from the GUI in browsers. In chess world this is totally normal, you have a chess GUI and a chess engine (and a crude communication protocol).
- my123 5y ago> I always wondered why the engine is not separated from the GUI in browsers For WebKit that's the case.
- kevingadd 5y agoAll the major browser engines can be embedded, the GUI is a separate layer. It's been that way for ages, even IE was this way.
- pseudalopex 5y agoGecko isn't really embeddable. Except on Android.
- burnte 5y agoGecko was ALWAYS embedable, it was literally designed that way from day one.
- pseudalopex 5y agoMozilla removed the embedding APIs in 2011. And they were incomplete and unstable before.[1] [1] https://groups.google.com/g/mozilla.dev.embedding/c/c_NMcO-N8wo https://groups.google.com/g/mozilla.dev.embedding/c/c_NMcO-N...
- burnte 5y agoThat's about being about to build out Gecko as a blob to be called like a library. That doesn't mean Gecko can be used without all the extra parts in your app.
- pseudalopex 5y ago> That's about being about to build out Gecko as a blob to be called like a library. That's what embedding a browser engine means. > That doesn't mean Gecko can be used without all the extra parts in your app. What extra parts?