[chromium]
It's faster than Firefox apart from on some ad-infested pages which take slightly longer to load the elements then hide them and it seems to do a better job at loading IE-only sites. Best of all it's open source which will keep the FOSS fanboyz happy.
I've come to the conclusion that WebKit>Gecko, it just seems lighter, faster and the fact that most WebKit browsers pass the Acid3 test seems to suggest better standards compliance too.
I love webkit. I was developing a poker heads up display that used webkit for rendering the hud (since im a web nerd, and since people like to customise their huds, and since using web technologies for this task is so sweet), and it could do some extremely sexy things for me combined with Qt. It's plenty light for the job for sure, and I wouldnt use gecko for the same task, given the option of webkit.
But I also love gecko. I use it almost every day on my eee pc to browse all over the web and it works like a charm. Now, using firefox 3.6 and catching up with new web technologies (because I wasnt up to dat eprobably since the last time i had an involved discussion here about it), I've got to call you up on your standards support remarks.
Firefox has
excellent support for html 5 video, while no other browser has any to my knowledge (unfortunately I know nothig about Chrome in particular). It also supports offline storage, downloadable fonts (does opera? please screenshot
http://www.alistapart.com/d/cssatten/poen.html it should have dotted font for 'css' 'zen' and 'garden'. I think I did this test before and opera passed, but i dont know for sure ), web workers, async javascript scripts (as of 3.6), ..
these features are big strides forward for the web. Particularly open video, because the web has developed a huge dependence on
Adobe Flash for this feature, and if you have the faintest idea of what the webs purpose is you know sombody needs to
take back the web.
I dont think referring to an acid test for obscure futuristic css properties is a smart way to compare standards compliance: it is for those specific standards, but thats all. I get 94/100 in acid 3 on FF 3.6, but what is firefox missing? There are particular things that might take a long time to sort out so that FF perfectly meets the specification, its a rigorous bitch of a thing to implement and I'm pretty sure noone intended for it to be implemented over night, but supporting the important bits such as gradients is necessary, and firefox supports all the major new parts of css that I understand. If you can aactually shed some light on the meaning behind 94/100, please tell me what features Firefox is lacking?