Linked by Thom Holwerda on Wed 13th Jun 2007 10:30 UTC, submitted by Francis Kuntz
Thread beginning with comment 247769
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2005-07-06
> for the purpose of speed
actually, they picked khtml due to its speed and extensibility. the speed improvements they did make were completely portable. the forking was to (a) allow them to develop in secret at the beginning and (b) avoid having to figure out how to abstract out their macos layer properly. it had nothing (zero) to do with performance.
> they would have simply used the kHTML trunk as-is
well, of course they couldn't do this as they wanted to port it to mac's native rendering system.
> Apple are not shoddy coders.
they are good coders, yes. they also aren't perfect and many of their changes have been questionable. nobody is perfect, so i object to people who try and defend projects (inc kde) as if they were.
> that the idea of porting Safari has arisen
safari, yes. webkit, no. webkit has been ported to various platforms for a few years now.
> Stop tub thumping just because it's Apple.
that wasn't why the 'tub thumping' happened. it was because it was usual apple "we don't really understand how this community thing works" showing its ugly.
it has since gotten much better.
giving someone (in this case apple) a get out of jail free card is as bad as putting them in there unjustly in the first place.
but let me guess .. you're a mac user and apple fan and you're not overly familiar with the free software roots of the platform you love?