Yes, they did have to release it as open source, as KHTML is LGPL, not BSD licensed. I don't believe for a minute that Apple is any more open than they are legally required to be, and even then only after some arm-twisting.
Yes, they did have to release it as open source, as KHTML is LGPL, not BSD licensed. I don't believe for a minute that Apple is any more open than they are legally required to be, and even then only after some arm-twisting.
LLVM, Clang, Darwin, libdispatch and many others are all liberally-licensed open source projects that Apple leads. More contributions are listed at http://www.apple.com/opensource/.
This isn't because Apple cares about software freedom, it's a simple calculation: these are components of the system that need to be high quality, but don't differentiate the product. If using and contributing to open source software makes the systems programming simpler, the business case has been made.
You would be right to point out that Gruber was mistaken in saying KHTML is BSD-licensed, but the rest is demonstrably false.
They were legally required to open source WebCore, derived from KHTML, because it is LGPL. And they did so, as soon as Safari was announced. They were not legally required to release WebKit, which is BSD. That release came several years later, and is certainly a more significant project than KTHML or WebCore alone are.
Too bad this was upvoted so highly because you clearly have no idea what you're talking about. Review the history of Apple's involvement in the project.
WebKit should remain freely usable for both open source and proprietary applications. To that end, we use BSD-style and LGPL licenses. Specifically, we aim for licensing compatible with LGPL 2.1+. We do not currently plan to move to LGPL 3. In addition, we strive to create a courteous, welcoming environment that feels approachable to newcomers. WebKit maintains a public IRC chat room and a public mailing list where the ideas of contributors both new and old are heard and discussed with equal weight.
Apple does provide the source for their blocks environment... But it's the type of code that probably has subtle platform-specific ABI dependencies. Who is going to port and verify it on all the platforms GCC supports?
Edit: And... yeah, they do go above and beyond, since there are bits in there that they've written and licensed BSD. If that code was encumbered by LGPL they wouldn't have been able to relicense it or claim original authorship.