News for hackers. Stuff that matters.
Re:Android now forces apps to include proprietary code for p... by soulofmischief on Monday June 10, 2019 @11:41AM (#20147745)
It's what I've heard rehashed around HN, but afaik the actual policy is more or less as described here:

https://forums.developer.apple.com/thread/18922

Essentially it works like it should anywhere else: If you don't publish source code and someone complains, you're out. In an ideal world Google Play would hold itself to the same standards.

However, the App Store does impart restrictions which are incompatible with GPL, so it's not so much that Apple doesn't allow it as it is that GPL doesn't allow it.

Apple has no official statement on this of course, but we know how they feel about GPL code given that they've removed every bit of it from their OS over the last few years.

Re:Android now forces apps to include proprietary code for p... by avar on Monday June 10, 2019 @12:04PM (#20147988)
They haven't been removing GPL code actively, they decided not to take the risk of using GPL version 3 software, so they've let the respective versions of bash, rsync etc. linger at their last released GPL version 2 releases.

E.g. Git is on GPL version 2 still (and probably forever), and Apple continues to update that in a relatively timely fashion.

Re:Android now forces apps to include proprietary code for p... by soulofmischief on Wednesday June 12, 2019 @03:31PM (#20168374)
Apple just switched to zsh, which is not GPL other than a few optional shell functions. Expect this trend to continue.
Re:Android now forces apps to include proprietary code for p... by pseudalopex on Monday June 10, 2019 @06:42PM (#20151591)
The App Store came after the GPL. Also, Apple could let developers opt out of the restrictions.
Re:Android now forces apps to include proprietary code for p... by soulofmischief on Wednesday June 12, 2019 @03:27PM (#20168352)
But they don't, and that's what this conversation is about.
Re:Android now forces apps to include proprietary code for p... by pseudalopex on Monday June 17, 2019 @06:33PM (#20208006)
You attributed the incompatibility to the GPL. Apple created the incompatibility. Apple could easily fix it. The FSF can't change existing versions of the GPL.