Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Stop whining and making excuses. Google managed to release Chrome despite all these so-called 'limitations'.
 
This.

Nintendo underpowers their consoles so that developers will find new and creative ways to utilize their hardware, and I'm sure Apple does the same, be it software or hardware limitations.

This isn't the same. Nintendo works within the limitations that they give their developers. The Wii's hardware doesn't magically improve when you insert a Nintendo disk instead of another developer's disk.

Apple, however, uses a faster JS interpreter in Safari than they allow developers to use in UIWebView. Thus Safari will always be a better browser from a JS performance perspective than any other browser.

Having said that, I am working on a browser for iOS and OS X which looks nothing like any web browser before it as a school assignment.
 
Stop whining and making excuses. Google managed to release Chrome despite all these so-called 'limitations'.

I don't think a company "whines." I think a company states challenges. People whine. And a lot of them in this thread alone.

Mozilla is making the best decision for them. iOS doesn't even need any more wrapped browsers.

I'm not sure I'd call it a loss for iOS since it wouldn't be able to be built the way it needs to.
 
Nitro (or a similar just-in-time compiler) in third party apps would mean they could put data into RAM and make it executable--a HUGE malware vector and source of risk. Unsigned native code can now run.

This shouldn't be a reason to restrict competition.

Apple should trust developers.

There is no reason why they couldn't allow others to make their own JavaScript interpreter - even if it was restricted in terms of how it could run.

If it's Apple's crippled interpreter vs. someone else's crippled interpreter, I bet the latter would win.
 
Last edited:
Firefox uses both a different Javascript and rendering engine than Safari and Chrome (which both use WebKit). It's not possible for Firefox to exist on the platform, with it's own Gecko rendering system, due to Apple's imposed restrictions. Don't compare Firefox and Chrome, it's two entirely different things.

Webkit is not a javascript rendering engine. Neither is Gecko.

The fact that chrome uses webkit as its RENDERING ENGINE means nothing. Chrome uses its own build, and doesn't share the one built into iOS. You can even compile chromium from source for iOS.

There is no limitato on iOS that prevents Gecko from running, other than Mozilla's own codebase possibly not being optimised enough for the iOS hardware.
 
Webkit is not a javascript rendering engine. Neither is Gecko.

The fact that chrome uses webkit as its RENDERING ENGINE means nothing. Chrome uses its own build, and doesn't share the one built into iOS. You can even compile chromium from source for iOS.

There is no limitato on iOS that prevents Gecko from running, other than Mozilla's own codebase possibly not being optimised enough for the iOS hardware.

This is not true.

If you want to do a web browser on iOS, it MUST use Apple's WebKit rendering engine - the one provided through UIWebView.

That's why Chrome for iOS is missing features that the Android and Desktop versions have.

Apps that browse the web must use the iOS WebKit framework and WebKit Javascript
 
I've never jail-broken any of my iOS devices (although the temptation to do so grows every time I read an article like this one). Is there any compelling-ly better browser available on Cydia (including some kind of semi-homebrew Firefox remix)?

IceWeasel for jail-broken iOS devices, anyone? :)

I'm not sure about that, but I do know that you can remove the Nitro engine restriction on jailbroken devices. You can also decide which browser is the main or default one.
 
Apple..its time for option to chose default browser.

This ability to make this option will be enforced sooner or later. Here in Europe Microsoft have been fined a couple of times now simply for not putting more effort to allow alternative web browsers. Just need the EU to step up!
 
That didn't stop Google from releasing Chrome.

Innovation, people. Don't let a limitation stop you from working with all the resources you have.

The thing is Mozilla has such limited resources that it is forced to be streamlined at all times. Fighting Apple on this is like jumping off a building and trying to fight gravity. Their energy is better spent elsewhere.
 
Nitro (or a similar just-in-time compiler) in third party apps would mean they could put data into RAM and make it executable--a HUGE malware vector and source of risk. Unsigned native code can now run. The only reason Apple allows this risk in Safari is because they can work to keep Safari free of security flaws that would allow exploits. Apple can't control that in other apps, so they're not opening the door to such problems.

That's the trade-off: speed vs. security. Apple has found a good compromise I think, but yes, JavaScript will run slower in third party apps--in other words, at the same perfectly acceptable speed Safari did before Nitro (only faster because today's hardware is faster).

This doesn't mean it's not worth making a third-party browser. And it doesn't mean Apple should open up Android-style security holes.

I bet the real reason is because it would be another vector for jailbreaking.

Apple is not that serious about security. They are more concerned with control over their devices. Look at how much effort Apple goes to make jailbreaking difficult. Example- some hardware feature has made currently made it impossible to downgrade iOS in newer iPads and iPhones.

Mac OS X doesn't have such restrictions and its security is great.

Don't be so naive and think Apple is doing it out of the goodness of their hearts.
 
That's not the story. It's not an artificial constraint.



Nitro (or a similar just-in-time compiler) in third party apps would mean they could put data into RAM and make it executable--a HUGE malware vector and source of risk. Unsigned native code can now run. The only reason Apple allows this risk in Safari is because they can work to keep Safari free of security flaws that would allow exploits. Apple can't control that in other apps, so they're not opening the door to such problems.

That's the trade-off: speed vs. security. Apple has found a good compromise I think, but yes, JavaScript will run slower in third party apps--in other words, at the same perfectly acceptable speed Safari did before Nitro (only faster because today's hardware is faster).

This doesn't mean it's not worth making a third-party browser. And it doesn't mean Apple should open up Android-style security holes.

Please. It is a way of keeping a monopoly on the device. Opening up Android style security holes and running unsigned code-you know, jailbreaking-would be a user choice. Apple refuses to allow anything on that might allow users of iOS devices to bypass the App Store, plain and simple.
 
That's not the story. It's not an artificial constraint.



Nitro (or a similar just-in-time compiler) in third party apps would mean they could put data into RAM and make it executable--a HUGE malware vector and source of risk. Unsigned native code can now run. The only reason Apple allows this risk in Safari is because they can work to keep Safari free of security flaws that would allow exploits. Apple can't control that in other apps, so they're not opening the door to such problems.

That's the trade-off: speed vs. security. Apple has found a good compromise I think, but yes, JavaScript will run slower in third party apps--in other words, at the same perfectly acceptable speed Safari did before Nitro (only faster because today's hardware is faster).

This doesn't mean it's not worth making a third-party browser. And it doesn't mean Apple should open up Android-style security holes.

This! I wish more people had a bit more of a clue about these sorts of things. Perhaps apple should allow apps to mark memory as executable then everybody would get to bitch and moan about the potential problems it could create. But hey at least there'd be a lucrative market in anti-virus for ios.
 
Release it on Cydia with Nitrous as a dependency.

I've never jail-broken any of my iOS devices (although the temptation to do so grows every time I read an article like this one). Is there any compelling-ly better browser available on Cydia (including some kind of semi-homebrew Firefox remix)?

IceWeasel for jail-broken iOS devices, anyone? :)

Nitrous basically does that for every browser. It removes the restriction that Apple put on other browsers and makes it as fast as safari.
 
iOS users lose yet again. As always Apple frowns upon their users having a choice.
Welcome in our walled garden!

:mad:

----------

Nitro (or a similar just-in-time compiler) in third party apps would mean they could put data into RAM and make it executable--a HUGE malware vector and source of risk. Unsigned native code can now run. The only reason Apple allows this risk in Safari is because they can work to keep Safari free of security flaws that would allow exploits. Apple can't control that in other apps, so they're not opening the door to such problems.
These problems exist already in iOS. The world calls the results: Jailbreaks.

That's the trade-off: speed vs. security.
That's nonsense. Safari on iOS is not 100 % secure. Not even the App Store connections were secure. So much for Apples secure platform.

iLOL
 
Shorter Mozilla org: "Wah, wah, wah, mean Apple won't let me..."

Maybe it would be an issue if mobile Safari was horrible, but it's not. If consumers are really jonesing for mobile Firefox then they should give the Galaxy S III a look. It's just that simple. That's how the marketplace works. A product doesn't offer a major feature you want, you look elsewhere.
 
iOS is so 1984.

-----

The limitations are there so that no other browser can truly compete with Safari. I'm sure if this article was about the browser restrictions Microsoft imposed many years ago, your stance would be the complete opposite.

Microsoft really didn't impose any browser restrictions, but Internet Explorer was installed on default and due to Microsoft's dominance that became an issue. So it's really not comparable to what Apple's doing, anyone could and can install another browser in Windows.
 
Please. It is a way of keeping a monopoly on the device. Opening up Android style security holes and running unsigned code-you know, jailbreaking-would be a user choice. Apple refuses to allow anything on that might allow users of iOS devices to bypass the App Store, plain and simple.

Running unsigned code and jailbreaking are not synonymous. Running unsigned code and increasing your risk of getting malware are.

I do, however, agree that the person you quoted's reasoning is flawed. If a security vulnerability is acceptable in Safari, why wouldn't it be acceptable in WebKit?

Maybe Apple will loosen the reigns with iOS 7 and allow other web browsers to displace Safari...
 
No other browser ENGINES are allowed, so what's the point of making just another cheap Safari wrapper?
Oh gee, how's about being able to open a 9th page on my phone without an existing one being silently tossed?
Everything else is just different UI on top of The lame old version of Safari.
I have both Atomic and Chrome on my phone in addition to Safari. They all work just fine. Any time I have to let someone else use a browser I fire up one or the other, so they can't blow away stuff I have up and want to stay up -- something I find that people habitually do on any device despite me telling them not to.
The problem is that Apple certainly wouldn't allow any of the Firefox plugin structure to work
You say that like it's a bad thing.

----------

The thing is Mozilla has such limited resources that it is forced to be streamlined at all times.
Having been the victim of core leaks in Netscape/Mozilla/Firefox for years I assert that streamlining and Mozilla have little to do with each other.

-----------

Apple should trust developers.
HAHAHAHAHA. "Developers" routinely write software that can't even handle an apostrophe in a name, as if they've never heard of Europe. Developers are among the last people I'd trust to not do something stupid.
-----------
iOS users lose yet again.
:rolleyes: I have three browsers ON MY FSCKING PHONE. All three more or less work (given how broken Chrome is on OSX I haven't used it much on iOS). In what way am I losing?
As always Apple frowns upon their users having a choice.
FFS, stop eating scabs off your foot, and grow the fsck up. Apple provides a mobile OS designed to give the user a positive experience. Part of that positive experience is being functional. Another is not having to run fscking AV on one's @#$@! phone because the manufacturer mistakes it for a desktop system. One facet of this is not trying to be all things to all people. If you want to dick around with your device rather than using it, and don't like OS updates, then WTF are you doing here instead of wrestling with some lame-ass Android POS?
It's a computer, the should be no restrictions that the user themselves didn't place.
Seriously? Examples of people who don't give a rat's ass about which of two Javascript things is used instead of the other:
o My wife (that's right, there are actual *GIRLS* in the world outside your mom's basement)
o 99+% of everyone else
 
Last edited:
Please. It is a way of keeping a monopoly on the device. Opening up Android style security holes and running unsigned code-you know, jailbreaking-would be a user choice. Apple refuses to allow anything on that might allow users of iOS devices to bypass the App Store, plain and simple.

Exactly. Why believe a technical explanation by someone who knows what he's talking about when there is a perfectly good conspiracy theory. :D


I do, however, agree that the person you quoted's reasoning is flawed. If a security vulnerability is acceptable in Safari, why wouldn't it be acceptable in WebKit?

It's not a vulnerability, it is an attack vector. That means, an attacker would say "so this browser is compiling Javascript and executing the compiled code. Maybe there are some bugs to be exploited that allows us to make the browser execute the code that I want it to execute", and then the attacker looks for vulnerabilities in this area. Apple apparently believes that they can avoid such vulnerabilities in Safari, but they don't trust other developers to do the same.


That's nonsense. Safari on iOS is not 100 % secure. Not even the App Store connections were secure. So much for Apples secure platform.

Well, that article claims what attackers could do in theory, but there is no evidence that attackers could do anything in practice. For example, the article claims that "in theory" an attacker could steal passwords; in practice, they couldn't.
 
Last edited:
I thoroughly enjoy the Firefox experience on my Nexus device...thanks to the Android OS.

Apple is a huge put off for me because of the limitations it puts on iOS.
 
I would have liked to see a Firefox type browser. Although I rarely if ever use firefox on OS X anymore.

----------

Stop whining and making excuses. Google managed to release Chrome despite all these so-called 'limitations'.

If there were no whining and making excuses, there would be no macrumors forum :)
 
2 things:

Firefox sucks. So who cares? Most people are fine with Safari, which has always worked perfectly well for me, and there other options.

Second, and this has already been put forward, but: if you don't like Apple's limitations of their iOS platform, don't get an iOS device! Get an Android, and find an app that will listen to your whining and utter consoling phrases from time to time. This is one of the core ideas that differentiates between companies like Apple and Google, and why the heck would Apple completely change their philosophy? Seems to be doing OK for them.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.