Being that the old thread was dated and lacking a poll option for Webkit, I decided to create a new one.

For the uninitiated, we stick to voting for best engine instead of best browser because there are simply way too many browser options out there.

What? nobody uses IE?

I use IE, but WebKit is my choice for best engine...

Gecko of Course!

WebKit.

An objective person would choose Opera or Webkit. Gecko has the best framework (FireFox and its plugin system) but as a sole engine its not as good as those two.

WebKit for me.

Gecko 1.9.

Gecko.

Presto is good and fast, but it's got a few rendering problems that annoy me.

WebKit is good and fast, but lacks support for some features while they spend more time adding new features.

Gecko is good and fast, and they're supporting CSS features before making their own new features (although SVG filters for web content look great, and I prefer that to the WebKit proposals)

Trident isn't good and it isn't fast, IE8 is better but it's still not good enough.

Opera > http://en.wikipedia.org/wiki/Presto_(layout_engine)

I simply love opera that I've been using for years. The fastest of all.

I wont talk about features here since it's about the engine

umm... the engine of Opera is called Presto, so it should be Presto (Opera) IMHO.

Anyway IMHO Presto is the best and Opera is my personal favorite browser.

Presto : Fast, compact, powerful, secure, standards-compliant, the only downside is that it's completely closed.

KHTML : Fast, compact, standards-compliant, completely open, however it's part of KDE, which is both a good and a bad thing.

WebKit : Fast, compact, standards-compliant, open, but its main app, Safari, suffers some great usability and security problems.

Trident : Open API, and it's trying... but still it fails in most other aspects.

Gecko : IMHO the prime example of what an open-source project should not become. The only positive thing about it is its open-source.

What?! So open-source programs should remain unpopular, unused and unsupported?! That's what your logic is saying.

Opera, yay!

Nope, you are completely wrong in your attempt of "mind-reading" my "logic", since WebKit is open-source, quite popular, widely used, well supported, and better than Gecko. So next time stop trying to play psychic mind-reader or put words in other's mouth

And what I'm saying is not just about the program, it's about the whole project

Well you haven't provided reasons, hence why people are asking questions.

"WebKit is better than Gecko" because?

I used to be an avid Opera user ... then for a while I went back to IE.... then Netscape... Now Mostly I use FireFox...

Tried Safari but the pages seem to Load Slower than IE.

does this thread require people to explain their reasons?

I don't see any reasons explained in


So I guess my reason of "WebKit is better than Gecko" is

For instance I don't like using Safari (Webkit) because Apple is generally slower at patching vulnerabilities than Microsoft or Mozilla.

Best engine = Opera

Agree 110%.

I don't really know how good the engine is but there's still too many websites that appear broken with Opera.
Got to say Opera 9.5 is better than ever before though.

well, I actually already mentioned it in my original post :

but then here we are talking about engines, not browsers, so some of Apple's funky non-sense UI decision and slow response to security vulnerability in Safari has absolutely nothing to do with WebKit. And WebKit now has spread to much wider areas other than Safari.

I prefer Gecko, to be honest.

Scirwode

I'm divided between Safari (Webkit) and Firefox (Gecko) for the Mac, but my ultimate vote goes for Firefox, as I find Flash and other plugins work better in Firefox and some web sites simply will not work on Safari.

As for Konqueror, it's OK, but the web page layouts did not always appear right the last time I used it over 3 years ago. Opera, I don't know it enough in order to give an opinion, but if I were to vote for the worst web browser/engine, I'd say definitely Internet Explorer! On the Mac, it's simply a rebadged version of Netscape and does not work at all on some of the newer websites! And on Windows, it's plagued with security problems (especially with ActiveX), slow, awkward (especially IE 7), not standards-compliant, and relies on too much propietary code.

+1

And remember we are talking about rendering engines not the browsers themselves.

WebKit for me. But I agree that Safari still has a long way to go in stability but for the engine WebKit is very good.

I vote for Gecko!

I voted for Geko because I use FX3, but IMO, I use mainly FX for it's GUI, not the engine, Presto and Webkit look really nice tho. (Who friking cares about never up2date Trident?)

I voted for Presto. Opera is the best and it runs really well.

Presto (Opera)

^ +1

After discovering the Google Chrome browser - Webkit.

Based on Javascript benchmarking and general performance in usage, FF3.1 by a long mile:

if you are using the FF3.1 with TraceMonkey on, then you should compare it with Safari with latest WebKit and the latest Chromium builds.

http://nightly.webkit.org/

http://build.chromium.org/buildbot/snapsho...ium-rel-xp/?O=D

Yeah, the latest WebKit nightlies with SquirrelFish Extreme should beat Tracemonkey by a bit.

Should modify the poll to show that Webkit is also a Chrome derivative, so uninformed people know

Definately my choice of browser, after Maxthon!

Gecko

I choose Gecko, but only because I haven't had the chance to use a WebKit-based browser, or Opera (Presto) long enough to compare them. Gecko seems to do the job for me, but others may be better.

Also, I'd like to know why/how 10 people (300+ in the other thread) have chosen Trident!?

There are no explanations in this thread, but surely people realise that the current final version isn't standards compliant and version 8 still has some way to go for Trident to be as good as other browser engines? Internet Explorer breaks many sites, including one I am currently developing which works in every non-Trident-based browser! I haven't got the time to change my code! If IE was standards compliant enough, it would work!

WebKit. The version with Chrome though, coz it's the fastest thing since a sneeze.
As a user, why should it matter to me whether the rendering engine of my browser is open source or not? It's not as if I'm going to rip it apart and start working out the bugs and make improvements myself. I'll still use how the people build it. So, open source or not, it's still closed to me.

Because, as a user, you surely would want the most efficient browser engine possible. With it being open source, the code is available to any of the public to develop off or improve upon. Eventually, with competition of other rendering engines and ideas from many developers out there who take advantage of the open source project, the rendering engine will become more efficient and maybe more effective.

That's why it should matter to you