Post a Comment
On a recent thread about Haiku's webkit port - someone mentioned this project, and I didn't think to go check it out, but now that I read it, that actually seems like a good strategy for Haiku's webkit browser project as well...
http://www.freelists.org/post/haiku-development/Who-wants-to-help-d...
MorphOS already has a working port, and its great!
http://www.morphzone.org/modules/news/article.php?storyid=1602
i hate to say it but Apple did a lot more than jsut polish. They added quite a bit more functionality as well. That being said, I personaly on not on the webkit bandwagon (though i do use the KHTML konqueror), I am also not a huge firefox fan either. I like Opera, but life is all about personal preference...
Apple did the hard work of decoupling KHTML from Qt & KDE, which is what makes WebKit so portable. Having worked on both the original KTHML port to AtheOS and the WebKit port for Syllable, the WebKit codebase is far, far easier to work with.
What's interesting is that Gecko was supposed to be the ultimate portable browser engine, but it ended up so bloated and with so many complex components that were required to be ported that it's pretty much only properly supported on three platforms, where as a pretty decent port of Webkit can be completed by one person in two or three months.
You mean for KDE? As webkit is based of KHTML from the beginning but they got so split of that they joined again under the webkit brand.
So give the love to the open source community as always and not for Apple. Sure they have contributed but only because they could benefit themself. I doubt they would had released their own open-source browser if they didn't based it on someone else work.



