Wednesday, September 3, 2008

Acid3 on Chrome

Is this good enough for a beta?

acid3 on chrome

I don't know if Google intends to have Chrome to be 100% compliant. By the way Safari scores 77/100 (using same Webkit rendering engine), FF3 scores 71/100 and IE8 beta 2 scores 21/100. If you like putting browsers on a race track see also this post for javascript benchmark test results. I also look forward to trying Safari 4 which allegedly could score 100/100.

Chrome has the simplicity I like on the outlook. It doesn't come with the font rendering I like in Safari but I think in due course those eye candy features will come either in the core or from plugins.

At first start up it didn't impress me because it took a long time to render Google's personal home page and crashed. Once a few pages are cached it was alright. In Task Manager I see few instances of Chrome, one for the chrome itself then one for each tab. There is also one for default functions such as shockwave flash etc. You can try ending those processes one by one and you'll know what has been terminated and taken away.

I have yet to see if it may suffer memory leakage so I'll start this for the whole day. Edited: I think Google is ready to show off. Chrome has its own Task Manager (press Shift+Esc) below and you can see which process is consuming how much. It's like Windows' Task Manager and you could end any naughty process that may be causing problem.


Try open a new tab and enter 'About:memory' in the address bar you'll see more about memory usage. Google is ready to show off, i.e. putting Chrome side-by-side with other browsers running. They know you'll be comparing are you not doing that right now?


No comments:

Post a Comment