Post a Comment
So what? ARM code can't run in x86 (without emulation) because architecture prohibits it. I don't have a problem with that. Apple forbids things not architecturally, but legally. If you don't see the difference - there is nothing really to discuss here.
Edited 2013-03-10 22:28 UTC
I think Kroc was implying that you can't run native applications in Firefox OS, so no other browsers implicitly as well. But it's a design restriction, not some sick legal prohibition so it's not comparable. It's like saying that JVM discriminates the native code.
Edited 2013-03-10 18:51 UTC
That's not a technical reason. For it to be a technical reason, there would have to be a full explanation as to why they do not allow JIT runtimes. Until then, it's a political restriction. They don't want someone like Google showing them up with V8 as opposed to Apple's own js runtime. It really is that simple.
That's a really good question in fact. I believe that the difference is that you can take Mozilla's Firefox OS and replace Gecko by the Web engine of your choice, provided that that engine implements the same Web APIs that Mozilla added to support the various things needed on a phone --- which has already started, with Samsung already adding some of these APIs to WebKit. By contrast, you can't take Apple's iOS and replace WebKit by the Web engine of your choice.
This isn't news. Apple banned all programs which can download and interpret code from the Web from even being legally built with iOS SDK like forever already? Which mostly boils down to browsers with JavaScript. This restriction is completely anticompetitive and deserves some serious antitrust measures, but Apple just gets away with it.
Just to clarify, the restriction is not in accepting these applications in the "app store" (even though they wouldn't be accepted if proposed most probably). The prohibition is in legally building them with iOS SDK. So if in theory someone could build these applications using alternative tools - this restriction wouldn't apply and one could distribute them through Cydia or something. But I'm not aware if such tools exist for iOS. Using development tools as an anticompetitive filter is completely ridiculous, but that's Apple, what else can we expect from them.
For the reference, some points in the iOS SDK license:
As a condition to using the SDK, You agree that:
(a) You will only use the SDK for the purposes and in the manner expressly permitted by this Agreement and in accordance with all applicable laws and regulations;
....
3.3 Program Requirements for Applications
Any Application developed using this SDK must comply with these criteria and requirements, as they may be modified by Apple from time to time:
....
3.3.2 An Application may not itself install or launch other executable code by any means, including without limitation through the use of a plug-in architecture, calling other frameworks, other APIs or otherwise. No interpreted code may be downloaded and used in an Application except for code that is interpreted and run by Apple's Published APIs and builtin interpreter(s).
Edited 2013-03-10 18:57 UTC
It is hard to sandbox this sort of thing. It would potentially open the door to apps doing things outside of what Apple's gate keepers certified.
An app could be a fart app, download and execute some code and become much more malicious.
That said, I think Apple (and MSFT) use a heavy hand here. On Windows Phone you can apply for a "Technical Exemption" which means, yeah I broke the rules, but I have a good reason for doing so.
Considering what a memory and resource hog Firefox is, I wouldn't install it even if they were creating it. Note that I'm not endorcing Apple's unfriendly tactics (although to be honest I don't feel an effect from them either) but, should Apple ever allow it, I'd be much more excited to install a version of Chrome with V8 than anything based on Gecko.
1. competition is good.
2. I believe Chrome as any browser can only use the existing already installed iOS libraries. So there is no v8 on iOS. They all use the same rendering- and javascript-engine. Even worse, HTML5 hybrid-apps aren't even allowed to use the full capabilities as you can with HTML5 in the browser on iOS. Let's just say Apple is pretty strict.
3. There aren't many benchmarks, but the ones I've seen show Firefox on Android is actually faster than Chrome on Android.
4. Firefox on the desktop usually uses less memory than Chrome these days (Chrome memory uses has increased, Firefox has decreased). Depending on addons it is still possible that Firefox will leak memory though, but these problems have become less and less of a problem they fixed most of those problems.
So I wouldn't just blatantly dismiss it.
Edited 2013-03-10 19:31 UTC
Sorry haven't read through all the comments. Just noticed the article.
Q. What about the "Junior" web browser which is a webkit browser developed by Mozilla?
I am excited about it and waiting for it.
Reference = https://www.google.com.au/search?q=junior+web+browser&aq=f&oq=junior...




