Linked by Thom Holwerda on Sun 6th Aug 2006 08:51 UTC, submitted by Moulinneuf
Apple "We all cheered when Apple began experimenting with community-driven, open source development for its flagship operating system. But if those experiments are now drawing to a close, should anyone really be surprised? In his columns earlier this year, InfoWorld's resident Mac aficionado Tom Yager noted how Apple seemed to be backpedaling away from open source. Seen through that lens, last week's news that the OpenDarwin Project would be closing its doors looks like just another sign of the times."
Thread beginning with comment 149580
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: not quite
by patrix on Sun 6th Aug 2006 16:57 UTC in reply to "RE: not quite"
patrix
Member since:
2006-05-21

"it's because KHTML is LGPL'd and WebKit is a KHTML fork so they *have to* release the sources."

If they had no desire to release the sources, they wouldn't have chosen an LGPL project in the first place.

Reply Parent Score: 4

RE[3]: not quite
by DeadFishMan on Sun 6th Aug 2006 22:26 in reply to "RE[2]: not quite"
DeadFishMan Member since:
2006-01-09

"it's because KHTML is LGPL'd and WebKit is a KHTML fork so they *have to* release the sources."

If they had no desire to release the sources, they wouldn't have chosen an LGPL project in the first place.


They didn't do it because they wanted to. They did it because they had no choice. It was either this (choose between KHTML or Gecko) or write their own HTML rendering engine from scratch. This is not a small feat, even for a company as big as Apple. They went the easy route and took something that was in a state that they could leverage for their own products.

Don't think even for a second that Apple wanted to share source code with anybody. They did it because they had to comply with the licence. That's all.

Reply Parent Score: 4

RE[4]: not quite
by evangs on Mon 7th Aug 2006 06:44 in reply to "RE[3]: not quite"
evangs Member since:
2005-07-07

Or purchase one from someone else? You forget there are companies like Opera and Omniweb who make their own browsers, who have their own rendering engine. There was no *need* to choose either Gecko or KHTML. If Apple felt that the LGPL was truly an issue, they would have chosen to go with something else.

Reply Parent Score: 4