If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Gecko vs. webkit

I'm not looking to start a flamewar. I've been trying to find out for a long time what the advantages and disadvantages over Gecko and webkit. I'm NOT referring to javascript performance because that's a separtate component. I've noticed a lot of developers seeeming to favor webkit over Gecko, including ones at Google, KDE, and Gnome, even though webkit is deveoloped by the evil Apple. Why? Is there something fundamentally wrong with Gecko? Is it harder to develop for? Is it inherrently slower because it's so much more powerful (instead of the more lightweight webkit)? I tried asking Mozilla and I got a political answer. I've asked elsewhere and they all talk about javascript performance, which is mostly unrelatted. Can someone give any real answers?

I can't promise that this is a "real" answer since I haven't worked directly with either engine, but I gather that Gecko is now designed predominantly as a component of Mozilla's XULRunner platform/core/environment, whereas WebKit's design is more friendly toward being embedded as a component in (relatively) arbitrary applications. The Mozilla concept is more that XULRunner handles all the heavy lifting and standards compliance minutiae while app developers primarily write XUL and JavaScript to define the user-facing functionality, which presumably doesn't confer enough power/control for the preferences/priorities of some developers/projects.

I'd be happy to be corrected by people with more direct knowledge if I've somehow misconstrued the situation.

That's part of what I don't understand though. Why did they choose to integrate webkit, but not Gecko?

Thats crystal clear, because Webkit is further development of KHTML, and KHTML was developed on KDE and used inside Qt for Konqueror web functionality.
So the origin of the problem was - why invent KHTML, when they couldīve used Gecko in Firefox 1.x era.