Google Returns Chrome To Beta, Touts Speed Boost
CWmike writes "Google yesterday reversed its decision to ditch the beta label from its Chrome browser, saying it is restoring the moniker to some builds to get faster feedback to developers. 'Since we took the 'beta' tag off Google Chrome in December, we've been updating two release channels: developer and stable,' said Brian Rakowski, a Chrome product manager, in a new blog Google kicked off on Tuesday. 'With our latest release, we're re-introducing the beta channel for some early feedback.' The first beta, Chrome 2.0.169.1, includes several new features, said Rakowski, and it boasts a significant speed increase over the current stable version of the browser, 1.0.154.48. According to Google's tests, the beta is 35% faster than the stable build when measured by the SunSpider JavaScript benchmark suite, and 25% faster on the company's own V8 tests."
Reader Al notes too that "Google has launched Chrome Experiments, a site where Javascript coders can upload projects that make use of Chrome's speed and processing abilities. The site already features a handful of cool 'experiments' including a balls that jump between browser windows, a gravitationally-challenged version of the Google homepage and a game that runs through nine different browsers. It's cool stuff alright, but some experts wonder whether browser security might be a more important thing to focus on."
It'd be nice if a company that prided itself on not being evil released the browser for more than one platform (dare I say, the evil one?)....
Cemil.
Just because a company's informal motto is "Don't be evil." doesn't mean they have to release their products for Linux.
Now I think it'd be unwise if they didn't release it for Linux, but it definitely doesn't make them evil.
Who wanted really fast JavaScript?
Chrome is not in beta, there has ALWAYS been beta builds around for Chromium & they are advertising those builds more since the new features are pretty solid (and the speed too) but Chrome is NOT in beta.
There are daily builds you could try. They're pre-alpha, though, so don't expect too much yet. Or you could build it from source, it's not too hard. See http://chromium.org/
One of the cooler ones I saw for Firefox 3.1b3 was real-time chroma-key replacement* in video. (i.e. The blue screen technique) Does anyone know if this new version of Chrome supports the video tag yet? I've been doing experiments with real-time video effects in Firefox, but I'd like to start ensuring that they're cross browser.
* I did my own version of the Chroma-Key replacement that ran a Javascript function for each pixel. It managed real-time playback even on slower PCs!
Javascript + Nintendo DSi = DSiCade
Google has not reversed their position. This is the beta for what will be 2.0 eventually. The 1.0 branch is and will be release. See: http://tech.slashdot.org/article.pl?sid=09/03/17/2345216
I find it vastly amusing the amount of press that browser "speed" gets (compared to trivialities, like, say, "usability in peoples' computer-based work patterns").
Ok sure, javascript engine speed might be important, but javascript clearly is inadequate as a rich-client development platform anyway.
I for one do not sit here on my macbook or my dual-core 2.6GHz 2G RAM pc and think to my self "damn these 70 browser windows and tabs are rendering slow - damn damn damn". No, I pretty much never have to think about that, thanks to good work done by hardware and software engineers over the last 15 years or so.
Speed is SO NOT the key issue anymore. Netbooks prove this. Usability in the context of always-on info and my persistent context and where the hell is the stuff I was working on etc. is way way more important as a surfing quality of life issue.
Where are we going and why are we in a handbasket?
Well, since no one cares about your opinion, e.g. "trash", just stuff it. Fact is, running on Linux will have little impact on the usage of Chrome.
Comment removed based on user account deletion
Maybe I'm in the minority here, but what's all the fuss with a "faster" browser, at this point? They're pretty damn fast as they are (pick one). The big problem, in my mind, is their memory use. That goes for both "normal running" memory use, and "my god it's leaky" memory use.
Currently, Firefox is running with 360M virtual and 131M resident memory utilized. The browser window has been open for 85 minutes with exactly 20 tabs - no flash, and 1 slashdot page. I've got to shut down firefox due to excessive swapping/poor system performance more often than I used to have to reboot Windows 9x due to stability issues!
Firefox, IE, and Opera have all shot up in their memory use extremely quickly - to the point where Firefox has become almost unusable on my laptop with 512M, while having Tbird and OO.org open at the same time. And that's only with about 20 tabs open, noscript, flashblock, and a bunch of other things to reduce the memory overhead.
Just because RAM is cheap doesn't mean you should leave people out in the cold who have older stuff. Likewise, if you bloat your products, porting them to portable devices (cell phones, etc.) is going to be a bit troublesome: RAM doesn't seem to be having the same speed or capacity leaps that CPUs are - and in a portable, sticking more RAM in is only going to decrease battery life.
~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers