News for hackers. Stuff that matters.
Re:Firefox for iOS on GitHub by fekberg on Thursday December 04, 2014 @09:46PM (#8702817)
How can Apple get away with that? I am genuine interested! Sounds pretty much like the same thing Microsoft did with Internet Explore back in the day, except they didn't force you to use their rendering engine, but shipped the OS with their browser as default?
Re:Firefox for iOS on GitHub by mkozlows on Thursday December 04, 2014 @09:54PM (#8702831)
Microsoft was a monopoly. Apple is a niche player. Antitrust laws don't apply to companies with 20% of the market.
Re:Firefox for iOS on GitHub by spigoon on Thursday December 04, 2014 @09:59PM (#8702840)
Actually, iOS has 42.4% of the smartphone market in the U.S. according to http://www.cnet.com/news/android-loses-some-us-market-share-...
Re:Firefox for iOS on GitHub by JohnTHaller on Friday December 05, 2014 @01:23AM (#8703212)
Still, Android has ~52% of the market. The antitrust laws used against Microsoft were due to the fact that Windows was nearly all of the market, both home and business. Plus, people using Apple now can switch off of it, unlike Microsoft at the time which had no viable options.
Re:Firefox for iOS on GitHub by cyborgx7 on Thursday December 04, 2014 @10:16PM (#8702869)
There are other markets than the US and the antitrust laws were employed against Microsoft in the EU.
Re:Firefox for iOS on GitHub by jfaat on Thursday December 04, 2014 @11:23PM (#8703008)
The US antitrust case[1] referred specifically to browser vendor lock-in.

[1] http://en.wikipedia.org/wiki/United_States_v._Microsoft_Corp.

Re:Firefox for iOS on GitHub by orbifold on Friday December 05, 2014 @05:35AM (#8703764)
As did the European case, ultimately forcing them to give a choice to the user which default browser to download, if I recall correctly.
Re:Firefox for iOS on GitHub by Cthulhu_ on Friday December 05, 2014 @04:00AM (#8703515)
Because their platform, their rules? IDK, I think it's perfectly acceptable to limit what you can do on someone's platform, since after all allowing anything on your platform will cause a lot of crap to appear - like a lot of stuff on the Android platform before it changed to the Play Store and Google started being a bit more strict about using their platform.

Restricting what developers can and cannot do on a platform allows Apple to give more guarantees and reliability in terms of performance and battery usage, as well as security and stability. Those are the primary reasons behind Apple's restrictions on the iOS platform.

Re:Firefox for iOS on GitHub by colordrops on Friday December 05, 2014 @04:40AM (#8703621)
You are only partially correct in your analysis. Yes, controlling the platform can lead to a better user experience. But how does banning browser engines lead to better app quality? It doesn't. If you look at the history of app store restrictions, you'll find that any app that provides an open platform or programming environment has been banned. That is because it takes the control out of apple's hands. It's a power grab.
Re:Firefox for iOS on GitHub by gress on Friday December 05, 2014 @11:17AM (#8705227)
It may be a power grab, but it also provides protection from malware that customers value.
Re:Firefox for iOS on GitHub by walterbell on Friday December 05, 2014 @01:40PM (#8706038)
Some restrictions do. Some restrictions have economic benefits for Apple.
Re:Firefox for iOS on GitHub by gress on Friday December 05, 2014 @04:06PM (#8706890)
This one has both.
Re:Firefox for iOS on GitHub by walterbell on Friday December 05, 2014 @01:39PM (#8706028)
What are the performance, security and stability benefits of removing native print-to-PDF functionality from iOS? It was supported by Apple in early iOS releases.
Re:Firefox for iOS on GitHub by chj on Thursday December 04, 2014 @10:10PM (#8702860)
I am equally surprised.