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.
Does that mean it's also okay to karma whore by re-posting highly rated replies to the original as long as you also link to them?
Come to pappa, sweet "+1, Insightful" mods!
Apple has a long, long history of acting irrationally, often to the point of blowing its own foot off and snatching defeat from the jaws of victory. They have a knack for choosing a course that is not in the interest of their customers, yet not in their own interest either.
Involving them in a project in a non-essential role is probably about the only way you can involve them at all. To rely upon them is to court disaster.
Lee
Muslim community leaders warn of backlash from tomorrow morning's terrorist attack.
the difference is that if you use Qt, theming is well supported from the bottom to the top, and no application can get past it.
with OSX, if you use carbon/cocoa, theming is a hack, not officially supported at all, and apps can get past the theming.
dont bother with the athena argument, its a red herring. you might as well argue about macos8. nobody develops new apps for either anymore.
let's see. if i use the 'official' frameworks on osx and i change themes with shapeshifter, and applications can get past the shapeshifter theming... this proves osx is somehow better?
qt/kde wants end users to be able to easily change themes to their personal taste, provides you easy and uniform ways to do it, and it is well supported. you're changing not only the application widgets, but also the window borders etc. for a completely consistent and uniform behavior.
apple is the complete antithesis to ui theming. they just don't want you to do it.