Posts Tagged ‘Google Chrome’
Chrome Beta for Mac/Linux Released
December 8th, 2009
Today Google finally releases a beta of Google Chrome for Mac and Linux. I've been using a Chromium build on my Mac for awhile now, and while it's faster than Firefox on the Mac, it's not nearly as fast and stable as the Windows version of Chrome. Also, without Google Gears for Mac OS X 10.6, Chrome and Google webapps are even less useful on the Mac. While I was on the road with my MacBook over the last few weeks, I found myself missing my desktop PC back at home only because of the more-stable Chrome and Gears availability. Will Gears for 10.6 will ever come out, since they're phasing it out in favor of HTML5? With features that depend on Gears like offline Gmail coming out of Labs, you'd think so.
Google Chrome Power User’s Guide
October 21st, 2009
Mentioned earlier this week that I've been rediscovering Google Chrome (mostly due to Wave), so this morning over at Lifehacker I rounded up some of its latest and greatest features in my Power User's Guide to Google Chrome, 2009 edition.
October 15th, 2009, 10 comments
Googler Matt Cutts tweeted a Chrome tip a few days ago that made me switch from the stable build to the developer version of Google Chrome. In it you can right-click on a tab and choose "Pin tab" from the menu. Like Firefox's FaviconizeTab extension (a favorite when combined with Better Gmail 2 and the PermaTabs extensions), that option shrinks a tab down to only its favicon and sends it to the far left, which saves you tab bar real estate. Note that pinned tabs do not persist between Chrome sessions.
Now that I've been spending a lot of time in Google Wave, I'm spending a lot more time in Chrome (because, you know, I don't use enough Google products). I miss my Firefox extensions, but in Chrome's dev version there appears to be extension support. Guess I should look into porting Better Gmail 2 and friends. In the meantime you can get early access to the developer version of Chrome here. (Thanks to Matt for the nudge to transition to Chrome's dev channel.)
September 22nd, 2009, 8 comments
After "countless hours" of work, the Google Wave team has thrown up their hands and decided not to make Wave work in Internet Explorer natively. Instead, they released Google Chrome Frame, an IE add-on that puts Chrome's backend inside Internet Explorer. Next week another batch of Google Wave invitations will go out, and IE users will have to install Chrome Frame or switch to Firefox or Safari to try Wave. (The screenshot is the prompt IE users will get when they try to log into Wave.) Google explains why Internet Explorer just doesn't have what it takes to run Wave:
Google Wave depends on strong JS and DOM rendering performance to provide a desktop-like experience in the browser. HTML5's offline storage and web workers will enable us to add great features without having to compromise on performance. Unfortunately, Internet Explorer, still used by the majority of the Web's users, has not kept up with such fairly recent developments in Web technology.
Read the rest »
I'm 
Logo by 
