Google Releases Chrome 2.0 Pre-Beta
Nick Fletcher writes "Just a few short months after the initial release, Google has released a pre-beta version of Google Chrome 2.0. It sports a few new features including form auto-completion, full-page zoom, 'profiles,' and Greasemonkey support. It seems the only notable feature would be profiles, which allows users to separate out their homepage, history, and bookmarks on a per user or category basis. It seems Google is still playing catch-up but they're definitely moving at a pace unknown to some of their competition. The full list of new features is available in the release notes."
Not too many exciting new features, I'm not sure why they call it 2.0.
Form autocomplete? It's about time. Not that I like the feature anyway, it's too dumb. 90% of the time it doesn't offer any suggestion (wild guess, if a web site asks for my name, maybe my browser might know the answer). The rest of the time (10%), it has a fifty-fifty chance of guessing right.
Full-page zoom and auto-scroll? Great. Now I can use Chrome like I use Safari on my iPhone. Of course scaling should scale the whole page, not just the text. It shouldn't be that hard. An old technology like PDF (10 years old) knows that.
Profiles? Ok, could be moderately useful. It sort of conflicts with the OS's notion of swapping between users. So I'd use it more as a workaround because bookmarks are hard to organize.
Greasemonkey scripts? That's my favorite. But it's for power users only. Just read the instructions and imagine your grandma giving it a try:
To enable this experimental feature you need to right-click on Chrome's shortcut from your desktop, select Properties and add --enable-user-scripts in the Target field. While you're in the Properties dialog, click on "Open File Location" and create a folder named User Scriptsin the user data directory, where you'll need to manually save scripts.
--
FairSoftware.net
Blogger Belzecue said on January 8, 2009 10:55 PM PDT:
Johnny Effyew here, lead strategist at Google.
Now, I hear a lot of complaints -- a helluva lot of complaints, actually -- about Google not supporting Linux, like how Google Chrome runs on Windows only. Sure, we're already up to version 2 of the Windows client with no Linux version in sight. That may be technically true, but I'm here to tell you, we built our entire company and fortune on the back of Linux and free, open-source software. So of course we support Linux just as much as we support Windows.
That's why it's my pleasure today to announce we've committed to delivering a native Linux Chrome client by 2015 or by the time the Windows client reaches version 10 or when Linux gains greater than 50% of the desktop market. That's our promise to every Linux user out there. You can take that to the bank. We know we have a moral debt to give back to the Linux community what we took from them and turned into a billion-dollar business. We know that.
But, as it turns out, writing software for Linux is kinda tough. We're still figuring it out. I mean, we all use Windows around the Google office, so it's not like we've got a bunch of internal people clamoring to use Chrome under Ubuntu or whatever.
And yes, we know there are much smaller companies out there like Dropbox who easily manage to code and release their Windows and Linux clients simultaneously, which is kinda like having your cake and eating it too. We think that's really cool, and we especially like cake. So that's doubly cool.
So hang in there, Linux community. Google Chrome for Linux is coming. In the meantime, just keep screwing around trying to run the Windows client under Wine. Good luck with that, hahahaha. Yeah, that should keep you nice and busy while we eat more cake and polish off version 3 of the Chrome Windows client. (Whoah, did I just say that out loud or think it? Pfffft, like those Linux fanboys will notice anyway.)
Folks, in closing let me say again: Google is committed to Linux the same way a tapeworm's committed to your lower intestine. From now on, when you think of Google and Linux I want you to think of me, Johnny. Think "Effyew, Linux! Effyew, Google!"
Gecko is large and unwieldy compared to Webkit. When Apple decided to build a browser, they hired ex-Mozilla developers, who promptly turned around and used KHTML because it was so much leaner and better designed, despite their extensive experience with Gecko.
It's far from obvious that Firefox is ahead in the technology stakes. It trails in many ways and seems like a far less agile project compared with Webkit and Opera. It does have a few areas where it is ahead, but the downsides seem like an albatross to me.
Bogtha Bogtha Bogtha
Hey, I know! We can have the email program have profiles too! And the photo editor, and the instant messaging client! Perhaps one day someone will come up with a unified way to have them synchronize, so that I don't have to create and manage a set of profiles on every application. It could also unify password management, and give each profile its own common place to put files.
Or, I don't know, we could actually use the user system that exists. Poorly reimplementing users in every single program is a horrible idea.
That said, there are uses for profiles that aren't just crippled reimplementations of the user concept. But they have more to do with wanting a different, well, profile of settings for different tasks -- things like the private browsing mode. Or, for example, I use a different Firefox profile for browsing Freenet (there are both performance and security reasons for that).
But it is all somewhat meaningless, whether Chrome passes ACID3 or not, since Chrome is meant to support a company that sells advertising.
I'm guessing that Chrome will never have AdBlock Plus and NoScript.
It's all about control. Firefox allows you to control what you read. Many advertising companies try to change readers into time-wasting, ad-reading, money-wasting robots.
Those who don't like being the target of aggressive behavior and want control over their lives will need to continue to use Firefox, no matter how technically superior Chrome is.