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.
Stop whining and making excuses. Google managed to release Chrome despite all these so-called 'limitations'.
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.
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.
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?![]()
Apple..its time for option to chose default browser.
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.
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.
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.
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.
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?![]()
Welcome in our walled garden!iOS users lose yet again. As always Apple frowns upon their users having a choice.
These problems exist already in iOS. The world calls the results: Jailbreaks.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 nonsense. Safari on iOS is not 100 % secure. Not even the App Store connections were secure. So much for Apples secure platform.That's the trade-off: speed vs. security.
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.
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.
Oh gee, how's about being able to open a 9th page on my phone without an existing one being silently tossed?No other browser ENGINES are allowed, so what's the point of making just another cheap Safari wrapper?
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.Everything else is just different UI on top of The lame old version of Safari.
You say that like it's a bad thing.The problem is that Apple certainly wouldn't allow any of the Firefox plugin structure to work
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.The thing is Mozilla has such limited resources that it is forced to be streamlined at all times.
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.Apple should trust developers.
iOS users lose yet again.
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?As always Apple frowns upon their users having a choice.
Seriously? Examples of people who don't give a rat's ass about which of two Javascript things is used instead of the other:It's a computer, the should be no restrictions that the user themselves didn't place.
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.
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?
That's nonsense. Safari on iOS is not 100 % secure. Not even the App Store connections were secure. So much for Apples secure platform.
iOS users lose yet again. As always Apple frowns upon their users having a choice.
Stop whining and making excuses. Google managed to release Chrome despite all these so-called 'limitations'.