Comments on: Open-source divorce for Apple's Safari?
Apple may be ready to ditch the open-source code behind its browser, leaving a sour taste for some developers.
Apple may be ready to ditch the open-source code behind its browser, leaving a sour taste for some developers.
December 27, 2009 9:15 PM PST
December 27, 2009 7:45 PM PST
December 27, 2009 4:50 PM PST
Add headlines from CNET News to your homepage or feedreader.
More feeds available in our RSS feed index.
Related quotes
First they admit the project had lanquished before Apple.
Then they all but admit that Apple had tried to work with them but they refused to accept the changes Apple wanted to make. Not 'pure' enough. Well, Apple has to get their product to market, it's part of something that is paid for and therefore expected to work, they can't let it 'lanquish'.
Now they whine because Apple gave up and moved on. Even though they still seem to be trying to work something out, still offering to merge their changes back.
Basically, the KHTML thought they could get something for nothing. Thought they could have Apple developers build up KHTML, but they could still have everything their way and not compromise. And now they whine.
Mozilla, FireFox,Opera, iCab. I could probably come up with dozens of others if I researched.
Personally I would like to leave stuff like this alone and let the market provide the Tools. If they don't, they'll get developers so angry, that
They won't want to develop anything, and they will have to develop everything Like MS does.
And Apple sure doesn't want to emulate MS.
- "Divorce" is wrong term -- this is a fork...
- by rdean May 15, 2005 3:28 PM PDT
- ...plain and simple.
- Like this Reply to this comment
-
Showing 2 of 2 pages (60 Comments)WebCore must remain open source under the terms of the LGPL, unless Apple purges all of the KHTML code from WebCore.
Here is the page:
http://developer.apple.com/darwin/projects/webcore/