5 ms·
I thought Mozilla said they were going to land some form of Firefox on IOS. Yep, here's the press release: https://blog.mozilla.org/press/2014/12/designing-a-
by EdSharkey 12y ago
I thought Mozilla said they were going to land some form of Firefox on IOS.
Yep, here's the press release: https://blog.mozilla.org/press/2014/12/designing-a-firefox-experience-for-ios/ https://blog.mozilla.org/press/2014/12/designing-a-firefox-e...
The actual work is going on here, but it sounds like it's only at the experimental stage: https://github.com/mozilla/firefox-ios/ https://github.com/mozilla/firefox-ios/ I'm kindof curious to build it and see if it works.
I read that the only issue with getting competing browsers onto iOS is the developer agreement says you can't provide a program with a proprietary javascript engine in it. Frankly, iOS is so big now, I would argue that that restriction strays into competitive advantage territory, and the OP is proof of that. If I were a lawyer at Apple, I would suddenly become magnanimous and get the developer agreement changed such that competing web browser programs _only_ may host their own JavaScript engines.
- azakai 12y agoIt is "Firefox", but it's still using the Safari rendering and JavaScript engine under the hood (like Chrome for iOS does), because there isn't an option to do otherwise.
- CHY872 12y agoThere are two problems. The first problem is political - firstly Apple make it so that you have to use the Webkit rendering engine for any third party browser. The second problem is more technical - iOS has memory protection that means you can't take a writeable page and make it executable. This means that you can't (for example) JIT compile Javascript (or any other language). Their built in exception to this is Safari. This is why Safari is faster than webviews.