First Look At Chrome 10 206
jbrodkin writes "Boosted JavaScript performance, Adobe Flash sandboxing, password encryption and an overhauled settings interface are among the new features in Google Chrome 10. JavaScript pages should now load 12% faster than in previous versions, and Chrome 10 beats IE9 by at least 50% in a JavaScript benchmark."
lol javascript (Score:3, Interesting)
Javascript benchmarkS? You mean chrome's own benchmark? Because it's scoring less in SunSpider, and it's certainly not beating IE9 in it. Not that this matters a whole lot, anyway.
one example of faster being slower (Score:4, Interesting)
Firefox is still faster in at least one real-world web app that matters to me. A free GPS smartphone app called Waze lets you edit and make corrections to the map by signing in to your account on their website. Their editor at http://www.waze.com/cartouche/ [waze.com] is where you make these edits, and Firefox is amazingly responsive with this web app. Chrome, on the other hand, has been getting more and more aggravating to use with this app. User input responsiveness has been getting worse and worse ever since Google starting making huge gains in their javascript performance. If I click on a road segment in Firefox it pretty much instantly gets selected and highlighted. There is a very large delay in doing the same thing in Chrome. In Firefox, if I click on some point in the map and drag to move my view of the map, the map starts moving right away. If I do the same in Chrome I get the same glacial delay before it starts moving the map, and every time you drag the mouse before letting go of the mouse button there is the same delay before your movement translates to movement of the map. In fact, any and all user interactions with the app involves an awful lot of delay. And why, I don't know. How come it's perfectly fluid in Firefox, and in Chrome it's an exercise in patience? If Chrome is *that* much faster, why is it an insane amount slower to edit Waze maps with it?
Re:I'll wait for Chrome 11... (Score:3, Interesting)
Cool story, bro. I'll wait a little bit until I get these same features in Chromium [wikipedia.org]. Won't take long.
It is good this way. You don't care about your privacy then you help Google advertise so you help fund the people doing most of the coding. The rest of us thank you for that. You do care about your privacy then you find yourself in a tiny minority that can be treated like a rounding error if you're an advertiser the size of Google.
This way everyone gets what they want. The world is more ideal than it often seems.
My accidental benchmark (Score:5, Interesting)
Last year, my daughter and I did a web page that generates mazes because she loves mazes and was amazed that I told her that the computer can be made to make one.
Trying it on IE8, I thought the page was broken. It took almost all day to complete what FF and Safari and Chrome did in seconds.
I then added some instrumentation and other HTML/DOM layouts to test the browsers. You can see this at http://sinz.org/Maze/ [sinz.org]
By the way, IE9 RC is much better but still an order of magnitude behind Chrome.