Results 1 to 7 of 7

Thread: Gecko vs. webkit

Hybrid View

  1. #1
    Join Date
    Jun 2010
    Posts
    250

    Default 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?

  2. #2
    Join Date
    Jan 2008
    Posts
    772

    Default

    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.

  3. #3
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,801

    Default

    I prefer WebKit because it's much easier to use. Qt has it integrated so I don't even need to do anything special to get it. Same goes for Gtk with its WebKitGtk module.

  4. #4
    Join Date
    Apr 2011
    Posts
    46

    Default

    Just by the way, WebKit is a fork of KHTML which is used in Konqueror. And it is open source, so it isn't only Apple that works on it.

  5. #5
    Join Date
    Jun 2010
    Posts
    250

    Default

    Quote Originally Posted by RealNC View Post
    I prefer WebKit because it's much easier to use. Qt has it integrated so I don't even need to do anything special to get it. Same goes for Gtk with its WebKitGtk module.
    That's part of what I don't understand though. Why did they choose to integrate webkit, but not Gecko?

  6. #6
    Join Date
    Apr 2010
    Posts
    1,946

    Default

    Quote Originally Posted by Prescience500 View Post
    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.

  7. #7
    Join Date
    Jun 2010
    Posts
    250

    Default

    So basically, they've choses webkit over Gecko, not because of technical superiority, but because of it's history?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •