3 ms·
They'd basically have to fork Firefox. There isn't a clear distinction between the engine and the browser. They had an embedding API at one point but dropped
by epage 6y ago
They'd basically have to fork Firefox. There isn't a clear distinction between the engine and the browser. They had an embedding API at one point but dropped it because the design made it hard to evolve both.
This is on top of people wanting quick market share which requires compatibility with the "big player" :(
- 2Gkashmiri 6y agouh,, arent these big players usually just reskinned chromiums only? whats giving them an advantage in terms of market share?
- nicoburns 6y agoThe point is that reskinning Firefox is pretty difficult because there's no stable API between the "skin" and underlying engine. Firefox used to have an option for embedding Gecko, but it's no longer maintained.