4 ms·
Chromium has been designed to be embedded in other applications. Gecko, as far as I've heard, is a clusterfuck to get working in anything but Firefox.
by ygra 8y ago
Chromium has been designed to be embedded in other applications. Gecko, as far as I've heard, is a clusterfuck to get working in anything but Firefox.
- realusername 8y agoThere's plenty of community forks of Firefox, if a few devs can maintain a fork on their free time, Microsoft has for sure the resources to deal with it.
- javagram 8y agoI don’t think forks are the issue. MSHTML and EdgeHTML are also used as embedded components in non-browser windows software. (E.g. you can write UWP applications powered by JavaScript and rendering UI using EdgeHTML). Gecko supposedly doesn’t work well for embedding in that context.
- _ZeD_ 8y agokhtml was designed to be embedded. I don't know about webkit/chromium stuff
- bwat48 8y agoI'm not a programmer myself, but it's my understanding that chromium is pretty well suited to being embedded. Just look at how successful chromium has been in this space, stuff like Chromium Embedded framework, Electron, the myriad of chromium based web browsers etc...
- hsivonen 8y agoWebKit was designed to be embedded. Chromium not really despite the CEF and Qt efforts.