News for hackers. Stuff that matters.
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.