jrick wrote:Am I like the only one here who actually *likes* KHTML?

Define "liking KHTML"

I personally find KHTML good enough - it offers a decent ad-blocking capability, it's pretty fast and generally renders pages properly. So while I use Konqueror for 95% of the sites, I do wish I didn't have to use something else (Firefox) for the remaining 5%.

I'm not debunking KDE's developers work on KHTML - WebKit was based on it. It's a good engine.

But Gecko has a better renderization and is faster, most of times.

I just think that KHTML is still not ready to be mainstream web-engine.

All I'm saying is that if we have WebKit, there's really no need to get Gecko. WebKit is pretty much on par with Gecko.

jrick wrote:Am I like the only one here who actually *likes* KHTML?

I use it daily - I don't really think about it which is a testament to it.

R_Rios wrote:I'm not debunking KDE's developers work on KHTML - WebKit was based on it. It's a good engine.

But Gecko has a better renderization and is faster, most of times.

I just think that KHTML is still not ready to be mainstream web-engine.

As a website developer I really hope for the day that there is only one engine, there will be no longer a need to test in every browser and make hacks to the markup to make the site work in certain browsers.

Which engine do I want everyone to standardize on? WebKit. It is the one that most closely follows the specifications for markup and languages and is usually ahead of everyone else in supporting the newer elements and styles. I want to design websites for tomorrow, not last year.

Let's try to stay on topic.