4 ms·
Personally I see the bigger issue right now as Apple. Apple basically has all their iOS users hostage to WebKit. Maybe we'll get lucky and Apple will lose the c
by tokyodude 8y ago
Personally I see the bigger issue right now as Apple. Apple basically has all their iOS users hostage to WebKit. Maybe we'll get lucky and Apple will lose the current app store case and another store will be able to allow other browser engines on iOS and hopefully that will light a fire under their butts so they start implementing all the missing APIs.
As a dev there are so many features missing from iOS WebKit and because iOS has such a huge market share I'm basically forced to design without those features.
I don't personally see the issue with one browser engine. It can be skinned differently and different features can be enabled or disabled. More people from more companies can contribute to the same basic engine. Kind of like so many Linux distros contribute to the same basic kernel.
- pcwalton 8y agoAgain: How do I get Chromium to accept our Rust code, in the world where it's the only browser engine?