> No, Apple is no saint in this story.
Nowhere did I say or imply that Apple was a saint. All I said was that LGPL allows linking with closed code and distributing the resulting work without having to make the closed code open, and that Apple could have structured WebKit in such a way as to keep most of their code from having to be made open.
This is the main difference between GPL and LGPL, and a big reason why the FSF now discourages the use of LGPL.
> The reason webkit is known today, and not KHTML, is because Apple ignored their LGPL requirements.
> First, they didn't publish anything for years.
They published their KJS changes in June 2002, shortly before they released products using it. They published their KHTML changes shortly after Safari was announced.
> Then only obfuscated source dumps with all comments removed for many years.
Citation needed. My recollection is that they published their code in the form that they used it internally. The difficulty for the KHTML developers in incorporating Apple's code was (1) WebKit was designed to do what Apple needed, which was not necessarily what KDE needed, and so the two were diverging, and (2) Apple was making a lot of changes that touched a lot of code making it hard to break it down to individual improvements that could be incorporated independently.
This made integration impossible.
First, they didn't publish anything for years. Then only obfuscated source dumps with all comments removed for many years.
It took ages until they published some source code, even longer until they opened their repository.
By that time KHTML was long dead, and development had centered on WebKit.
No, Apple is no saint in this story.