Linked by Thom Holwerda on Mon 9th May 2011 21:46 UTC
Apple Apple has released the source code for WebKit in iOS 4.3, which it had been withholding for eight weeks. However, according yo Jay 'saurik' Freeman, they are still not, and never have been, in compliance with the LGPL. "Apple's provided source code (which /is/ heavily modified for the iPhone) [...] isn't even complete enough to compile (it is missing a bunch of code for the WAK* classes), so Apple has simply never been in compliance with this license," Saurik writes. So, it would seem that Apple is still violating the LGPL, and has been doing so for a very long time. Funny how this never makes it to mainstream technology sites. I guess they find their pre-release review devices more important.
Thread beginning with comment 472642
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:


"But I repeat: even if Apple is in violation, how are end users harmed? Even assuming that released source code is a benefit that end users want, not receiving a benefit is not, per se, harm."

I don't know the details of what apple is withholding, or whether there is in fact a violation. If there is, then we can agree that apple should be held accountable for it.

Never the less, if apple is in violation, your logic is absolutely wrong that it doesn't hurt end users. Not understanding this implies that you don't understand how the LGPL is designed to protect end users as well as the developers.

"So tell me: if I buy an iPhone and use it, how am I harmed by not having the source code to WebKit?"

It disturbs me greatly to hear the claim that GPL violations don't harm any end users.

"But end users, by definition, don't depend on access to source code. Source code is useful only to developers. "

By definition???? Many of us "end users" are developers and/or homebrew users.

Users wanting to patch & recompile, or even just inspect the source code are prevented from doing so because of apple's (alleged) infringement. A developer's reasons are technically irrelevant to this discussion, but could include security enhancements, new customized features, code review to make sure apple's not hiding back doors, incorporation into other projects, homebrew development, etc.

While you dismiss source code rights nonchalantly, many of us are harmed by not having access to the source which we are in fact entitled to.

"Actually, this is a boring question because it's easily answered. At no point is the copyright holder ever 'gone.' When people die they transfer all their assets, including held copyrights, either in accordance with a will or other instrument, or in accordance with local law."

I appreciate your infinite wisdom, but you didn't give the question the due consideration that it required.

I specifically mentioned the copyright holder dying before they've had the opportunity to set a successor. If there are no decedents to inherit the rights, then what happens? Does the state take ownership? The state can't revoke outstanding GPL licenses, but it's not under any obligation to enforce it either. If the state owns it, conceivably the code could become public domain, in which case companies have an easy out for avoiding their GPL obligations.

"From my perspective, Apple does, as you say ride on the work of a lot of people. But those people all agreed to have their work be used in accordance with the license they chose."

Re-read your posts, you suggest that even if apple is in violation, it doesn't harm users... on a site like this those words could be considered trolling.

Reply Parent Score: 1