backtop


Print 24 comment(s) - last by kaosstar.. on Feb 28 at 11:51 AM

New build brings GPU acceleration, synced passwords, beefed up Javascript performance

Internet Explorer 9 looks to make up much ground for poor previous outings by Microsoft browsers.  But even as it remedies slow performance and lacking standards, IE 9 is threatened by a slick set of super-fast browsers from smaller third parties who don't happen to be named Mozilla.

Among those challengers is Google's Chrome 10, which was just released in beta form last week.  Like IE 9 and Firefox 4, Chrome adds the much desire GPU hardware acceleration to Google's framework for the first time.  According to Google's blog on the release:

In full screen mode, CPU usage may decrease by as much as 80%!

Other major improvements have been made to Chrome's core Javascript engine.  Dubbed V8, the new engine offers 66 percent improvement in the company's V8 benchmark suite over the version found in the last stable build.

The new version of Chrome also introduced synced passwords, which allows you to share passwords across your (possibly) many computers.  The system includes passphrase protection, so your passwords are less likely to fall into the wrong hands.

Aside from speed, Chrome looks to hold an edge over IE 9 in HTML5 and CSS3 standards support.  Chrome 10's beta scores a mean 288 in the html5test.com (beta) metric, versus 255 in Mozilla Firefox 4 and 130 for IE 9 [source].

Google needs to put its best foot forward with Chrome as the company is going to use the browser as the basis of its upcoming operating system.  Built atop a base Linux kernel, the browser-centeric operating system should prove a unique competitor to Microsoft's Windows operating systems.

Web Store was recently added to Chrome in preparation for the release of Chrome OS.  The web store allows developers to write web apps (games, music players, etc.) in languages like Javascript and PHP and sell them or offer them in ad-supported form.

Chrome 10 can be found here.



Comments     Threshold


This article is over a month old, voting and posting comments is disabled

Hardware acceleration fail
By phatboye on 2/21/2011 3:59:45 PM , Rating: 2
So if my memory serves me correct Chrome's implementation of hardware acceleration will not be based upon OpenGL but instead will use MS's proprietary Direct X API thus this new feature will not work on non-MS OS'es.




By JasonMick (blog) on 2/21/2011 4:17:51 PM , Rating: 2
quote:
So if my memory serves me correct Chrome's implementation of hardware acceleration will not be based upon OpenGL but instead will use MS's proprietary Direct X API thus this new feature will not work on non-MS OS'es.


I'm sure Google has a OpenGL implementation in the works... after all Chrome OS isn't exactly going to have Direct X onboard...

I can feel your pain, though, I frequently use Linux boxes and might consider switching from Firefox if Google offered decent hardware acceleration.


RE: Hardware acceleration fail
By B3an on 2/21/2011 4:29:27 PM , Rating: 2
Firefox also uses DirectX ... on Windows. And now Google does, simple because, it's faster, better, and so are dev tools and drivers.


RE: Hardware acceleration fail
By MonkeyPaw on 2/21/2011 5:57:11 PM , Rating: 1
I don't really care for FF anymore. It doesn't seem to manage resources that well, and it's been much more crash happy since after version 3.0. I like how simple Chrome is, and I can't remember the last time it crashed on me.

Anyway, I'm sure OpenGL support will remain where it is needed. After all, OSX also uses OpenGL for video acceleration, too.


RE: Hardware acceleration fail
By Kurz on 2/21/2011 7:59:47 PM , Rating: 2
Check to see if your plug-ins are updated.


RE: Hardware acceleration fail
By Totally on 2/21/2011 11:44:37 PM , Rating: 4
Experiences differ, I literally could take your statement and just swap FF with Chrome, vice-versa. I rarely use chrome and almost it always crashes where I use Firefox all the time and it rarely ever does.


RE: Hardware acceleration fail
By bug77 on 2/22/2011 3:57:25 AM , Rating: 2
Unigine Heaven will disagree with you. It scores exactly the same with either OpenGL or DirectX11.


RE: Hardware acceleration fail
By AnnihilatorX on 2/22/2011 4:39:21 AM , Rating: 2
OpenGL performance and stability depends a lot on GPU especially drivers.


RE: Hardware acceleration fail
By bug77 on 2/22/2011 5:38:32 AM , Rating: 2
And DirectX performance doesn't?


RE: Hardware acceleration fail
By kaosstar on 2/28/2011 11:51:16 AM , Rating: 2
Linux users, who, aside from Mac users, will be the only ones requiring OpenGL support, get terrible drivers from AMD (ATI), but usually decent ones from Nvidia. Windows users almost never have to worry about GPU driver stability, unless maybe they have bleeding edge hardware.


RE: Hardware acceleration fail
By kevinkreiser on 2/21/2011 7:22:34 PM , Rating: 2
I did some work on a webgl app and used ubuntu with the latest beta of chrome. Webgl (based on opengl es) worked like a charm. I'm pretty sure if they want to, they can offer gpu accelerated rendering of pages in non windows os's via opengl since they must have implemented webgl functionalities using it.


RE: Hardware acceleration fail
By omnicronx on 2/21/2011 10:49:00 PM , Rating: 2
Actually if memory serves its the exact opposite for the very reason you mentioned.

Unlike FF(for windows at least) and IE , Chrome's acceleration would be OpenGL based, which would explain why they added the 'in full screen mode' portion into the 80% improvement.


RE: Hardware acceleration fail
By omnicronx on 2/21/2011 11:05:35 PM , Rating: 2
Well i guess my memory does not serve me well =/

DX9 acceleration vs Direct 2d/other technologies for FF/IE


"I'd be pissed too, but you didn't have to go all Minority Report on his ass!" -- Jon Stewart on police raiding Gizmodo editor Jason Chen's home














botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki