Safari vs. KHTML

Johnny Mnemonic writes "CNET has a story that describes the divergence between the code base of Safari and KHTML. Although there were high hopes that Apple would contribute significantly to the OSS project, that optimism has all but disappeared. Is an unrealized danger of OSS that others may take your project in a direction you didn't intend? Can OSS code and goals harmonize with the goals and needs of corporation designed code? Is it that Apple mismanaged the relationship, or that the KHTML guys expected too much? Interesting warning for other OSS-corporate marriages." We've previously reported on the frustration in the OSS community on this issue.

Comments

I see nothing wrong with it

[bogie]

There is no clause about having to spoon feed your patches back into the project you took your code from.

And in fairness to Apple I don't see as nearly as many articles from them saying how "well they work with OSS" vs articles complaining that they don't work well with OSS from OSS users.

That said I do wish Apple zealots would stop raving about how well Apple does play with OSS. They IMHO are the root cause of all of the bad will. If they would just shut the hell up then we could look at Apple as what they are, a passive OSS user. Instead everyone yelling about how they don't play nice. Yes Apple doesn't help out with OSS as much as we'd all like, surprise. Let's move on and spend our time talking about the companies that do help.