First Look At Chrome 10
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."
...because it's 1 version more.
There's no -1 for "I don't get it."
I remember installing Chrome when it first came out and them almost immediately uninstalling it. Either it or Symantec EP had a bug, and the browser window would immediately crash. 9 versions later... these guys have made an absolutely incredible product. I simply don't know what I'd do without my bookmark sync. Their app store needs some work, though, right now it's more of a bookmark store.
Ack! TFA is a seven or eight page "slideshow" that has pretty much zero actual comment. What a waste.
And I actually really LIKE Chrome (on the PC; Opera on the phone).
Three Squirrels
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.
huh?
ive been running chrome on ubuntu for ages now and never ever had even one issue with it. im actually running the unstable versions and theyre perfectly fine.
i cant see your problem
TFA is a little thin - it is basically a slideshow.
Still, IE9 beats out Chrome 10 in webkits own sunspider benchmark. On my old rig:
IE9: 348.2ms +/- 0.8%
Chrome: 446.0ms +/- 1.9%
Reading slashdot one-liner: (irm http://rss.slashdot.org/Slashdot/slashdot).rdf.item | fl title,desc*
You might be able to pretend you're not running complete junk. The benchmark should use a heavy Slashdot comment page. If it can load in three seconds, you gotta winner.
For justice, we must go to Don Corleone
Chrome 10.0.648.127 beta and Ubuntu jiving just fine over here...
After a clean install, I installed the stable version on another machine yesterday, through the commandline, even!
http://www.ubuntuupdates.org/ppas/8
"Google Releases Stable Version of Chrome 10"
Is it really this hard for /. editors to use the handy little search function this site provides and see if a story is a dupe? This story was even posted two days ago (albeit on a different website but it's pretty much the same thing).
"Our country is not nearly so overrun with the bigoted as it is overrun with the broadminded." -Archbishop Fulton Sheen
<breathless>JavaScript pages should now load 12% faster than in previous versions, and Chrome 10 beats IE9 by at least 50% in a JavaScript benchmark.</breathless>
I just came in my pants! 12% faster!
Perhaps you should try Chrome 10 - it's out now you know.
dnuof eruc rof aixelsid
Because people like you who turn JavaScript off are tiny minority of users. Almost everyone else actually uses and enjoys it.
Anyone who loves or hates any language, platform, or manufacturer, doesn't know what they're talking about.
Written by John Resig for Mozilla:
http://dromaeo.com/
I'm interested in seeing how much DOM manipulation improves w/ Chrome 10.
I'm still waiting for NoScript, so I can use Chrome without being blasted with pop-unders and unwanted noisy video ads. Until then, I'll suffer the slowness of Firefox.
Almost everyone uses it. Few enjoy it.
Gone!
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/ 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?
Does it have a master password yet? Until then there's no way I can use it.
Though the 7 slides in TFA contain almost no content at all, this was in fact one of the questions answered: yes, they now have a master password.
On Windows it uses the Windows encryption services so your login password is effectively your master password.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
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/
By the way, IE9 RC is much better but still an order of magnitude behind Chrome.
To be clear, I don't work for Google. I meant that the identity of my employer is irrelevent when I've got objective statistics backing me up.
Anyone who loves or hates any language, platform, or manufacturer, doesn't know what they're talking about.
Last time I checked I could not use Chrome for browsing documentation loaded from the local disk. This is the most innocent HTML application imaginable - just a frameset with the navigation panel on the left (TOC, Index, etc.) and the actual contents on the right. And Chrome will not allow one frame (e.g. the TOC) to load a page in another frame because it is a security risk. Duh...
Awsome !
All those things I'll be able to do during those precious milliseconds... !
Seriously, stop about the stupid javascript speed race, and focus on user experience, protection of privacy.
Ha damn, we are talking about Google... User privacy is their currency.
Well good if it pushes competition to improve, other than that I am not sure what to get out of it