Google Releases First Pre-Beta of Chrome 2.0
The Google Chrome team keeps releasing updates to Google's browser on an almost weekly basis, but it is interesting that the latest version in the developer channel is now already being called 2.0. This comes just about four months after Google first released its browser to the public. This new version (2.0.156.1) is only available in the developer channel, but it already points at where Google is planning to go with this next version of Chrome, which, besides many new features, also includes a new version of WebKit and Google's own implementation of the HTTP protocol.
For us, this new version worked perfectly, but others had a different experience. If you want to try out the latest versions of Chrome, you can find instructions for how to subscribe to the development channel here.
New Features
Here are some of the features the team added since version 1.0 became available:
- new version of WebKit, with bugfixes and new features, including CSS gradients and reflections
- bookmark import from Google Bookmarks: this is still only a one-way street, so you can't actually sync bookmarks yet, but we would be surprised if somebody on the Chrome team wasn't working on this
- form autocomplete
- tentative support for Greasemonkey scripts: you have follow these instructions, and not every script will work (for us, only about 1 in 3 worked), but it's a start. Hopefully, Google will include a UI for managing user scripts in one of the next versions
- autoscrolling: works just like in IE or Firefox - just hit the middle button and drag the mouse
- full-page zoom: this resizes the text, as well as images and embedded objects
- better spell-check with the ability to quickly change languages
Dragging Tabs
One feature that stands out, because it is reminiscent of what Microsoft is doing in Windows 7, is the ability to dock dragged tabs. Now, when you drag a tap to the edge of your monitor, a small icon will appear and, depending on where on the page you release the mouse, the windows will be maximized, or be aligned with the respective edge of the monitor.
HTTP for Windows, Mac, and Linux
Google also included its own HTTP network code in this new version, which, according to the release notes, was necessary to move ahead with the Mac and Linux versions of Chrome.
Security
Google also introduced a new secure browsing mode that forces HTTPS (you have to invoke it by starting the browser with --force-https. Just last week, we bemoaned that Google itself often doesn't use SSL as the default for its own apps. By setting this mode, you can be sure that you will be (relatively) secure.
ShareRelated Entries
1 TrackBacks
TrackBack URL for this entry: http://www.readwriteweb.com/cgi-bin/mt/mt-tb.cgi/9721
Comments
Subscribe to comments for this post OR Subscribe to comments for all ReadWriteWeb posts
Looks great, but I have not yet jumped on the Chrome bandwagon. It took years for folks to wise up to Firefox, and even there they still lag behind IE. I just don't see the need for another browser ...
But, like any Google product, they stink at first and then come out on top in a matter of years, so hopefully these changes for 2.0 will lay the ground work for future success.
fwiw a pre-beta release is known as an alpha release
Chrome is the best browser out there. Long been a fan of Firefox but Chrome is now my browser of choice.
So when will they bring add-ons into the mix? Until they do that, it doesn't matter how many bugs they fix, or UI tweaks they make, they won't be able to compete against IE or Firefox effectively.
I really like Chrome but until it has full extension support like Firefox, I won't be making the switch. There are too many essential extensions I just can't live without!
Can't wait until this does happen though!
I'm still waiting for them to release a Linux version.
Like Colly, I also wait for the Firefox extension support. I use and simply cannot work without some of them.
I think the most important and interesting question will be the choice of implementing the Firefox API and to be completely Firefox-compatible (seems to be quite tough), or release a similar but different API (this seems to be easier, but practically useless, it would be similar to a Linux-Windows world, Chrome being the Linux).
Having the userscript support (realm of Greasemonkey) is a bad news for me, because if they supported the Firefox-compatible version, they wouln't release a builtin Greasemonkey instance.
Posted by: kgyst.myopenid.com
|
January 9, 2009 8:31 AM
I severely doubt Chrome will ever support Firefox extensions natively. The Firefox rendering engine renders it's own interface. This is a large part of the reason extensions have so much power and work so well for Firefox. Internet explorer supports addons, but these are much less feature-rich and much less numerous than Firefox's offerings, because of this.
Chrome is built on WebKit, so it's a bit of a jump to imagine a Firefox addon working. Period. That's not to say that Firefox addon developers won't port their extensions to Chrome, but I'm pretty sure it will require them porting it. Even then, I think Chrome is more likely to end of on IE's side of extension: limited UI changes and more difficult or impossible integration of advanced features.
All that said, if a Mac and Linux version doesn't roll out with 2.0, I'm going to me more than a little irked. I'm still annoyed that we were skipped the first time around. Considering that the development community is much more prevalent on the Mac and Linux side (the same group most likely to use Chrome), it was a huge misstep to develop solely for Windows.
I like and use the hosted apps (Gmail, etc). As Mac user, Google regularly shows me that they could care less about the platform...Picasa for Windows was out for how long before a Mac version hit? Chrome is in alpha for 2.0 on Windows, but there's nothing about Mac?
In the mean time I'm happily using FF3.1b2... they've had a Mac version since it was Phoenix 0.2. Thanks, but I don't feel like being a second class citizen.
Extensions for Google Chrome will arrive later this year. Mac and Linux version are expected in 2 months (most likely less).
Thanks for the update.
We're all quite interested in what the goog's doing with WebKit. This is Read Write Web; great, deep(-ish) tech writers writing for a great, deep(-ish) tech audience. If you state the latest Chrome release includes
you should likely explicate - right there - what you mean by that. Have they actually reïmplemented hypertext transport protocol?
I don't want to be too much of a dick, but my laptop (not a PC computer) is in need of plugging into the AC current outlet, but first I need to get some cash from the ATM machine.
I *will* run Chrome on the Mac and Linux. And, again, thank you for this update.
Why is no one talking about the political implications of the Chrome-Firefox showdown?
Firefox is open-source, transparently-developed software. Surely it is a major achievement that the new de-facto software platform for the web (the browser) is controlled in this way.
Competition from Chrome is healthy, but let's not forget Firefox is also a political project, about freedom and control of data.
Chrome is very very quickly but design is bad
I love Chrome. Have used it since it was launched. Looking forward to new add ons to make it a bit more friendly. I have been able to use the bookmark toolbar, to access all the sites for posting and commenting.
It has a lot of Real Estate room, I just hope they don't clutter it up like every other browser has.If I need more, I surf on Fire fox, for now though, it's a breath of fresh air..great post.