Comments on: Google says it can keep Chrome on top

By: David Wright

David Wright — Wed, 17 Sep 2008 11:55:26 +0000

Matthew, I know what they are (I’m a web developer by trade).

But surely ironing out the quirks (and feeding them back to Safari) is a better way to do things than to leave the quirks in there.

It is irritating having to break the site for IE6 anyway, but if all the browsers strive to get rid of the quirks, the world would be a much better place, at least from where I am sitting…

By: Paul Mison

Paul Mison — Wed, 17 Sep 2008 10:28:49 +0000

I don’t think Firefox should necessarily be abandoning its JavaScript engines and development: John Resig’s post-Chrome benchmarks shows Tracemonkey isn’t that far behind V8.

What really depresses me is the absolutely awful performance of IE7 and even IE8, including not even being able to run some of the benchmarks because of missing features, and being far slower on the tests it can complete. It’s easy for Chrome to take share from Firefox, but that won’t help the web. It’s IE that’s the real problem, but I fear the big blue “Internet” oan the desktops of non-technical users will hang around for far too long.

By: Matthew Sparkes

Matthew Sparkes — Wed, 17 Sep 2008 09:47:40 +0000

The bugs were introduced so that pages rendered the same for Chrome as in Safari – that way there were no headaches for web developers. Don’t think of them as “bugs” exactly, more like “quirks”!

By: David Wright

David Wright — Wed, 17 Sep 2008 07:18:09 +0000

>>“We even implemented bugs, as long as they weren’t security bugs,” said the developer proudly.

Berk! Surely the correct thing to do – WebKit being an open source project – would be to correct the bugs and pass the changes back to the WebKit team to implement in Safari and the other WebKit based browsers… :-S

By: Ujjawal

Ujjawal — Tue, 16 Sep 2008 23:26:29 +0000

http://www.gadgetgyan.com/the-news/1-latest-news/281-first-look-at-google-chrome.html

By: Ujjawal

Ujjawal — Tue, 16 Sep 2008 23:23:14 +0000

I don’t know but more features might make this slower than others.

By: Sameer Alibhai

Sameer Alibhai — Tue, 16 Sep 2008 19:26:32 +0000

Firefox has already made claims that their new javascript engine, to be released in the next Firefox – codename TraceMonkey kicks Google’s V8 butt: http://arstechnica.com/journals/linux.ars/2008/09/03/new-firefox-javascript-engine-is-faster-than-chromes-v8