I've been a heavy user of Google Reader for over seven years, so I was a little upset yesterday when I saw that, buried in a "spring cleaning" blog post,…
Five months ago I wrote about the Cr-48 Chrome OS notebook prototype I had received from Google. I’ve been using it almost every day since then and was planning on giving an update after six months of having it. But, at Google’s IO conference last week, they announced the availability of Chromebooks for purchase beginning June 15th, so I decided to share a few thoughts while Chrome OS is getting some extra attention.
At a press event three days ago (December 7th), Google provided a long overdue progress update on the status of their Chrome OS project. No, it wouldn’t be shipping on new laptops this year like they had previously promised. Instead, Google announced a pilot program where they would provide participants with notebooks running the Chrome OS in exchange for using it often and providing detailed feedback.
Figuring it was worth the few minutes it took to fill out the application form, I signed-up for the Chrome OS pilot program. So with my low expectations in mind, yesterday I was shocked to find that a Cr-48 notebook had been delievered to our house by Google.
Below, I’ll give you a quick overview of the Cr-48 prototype notebook and of Chrome OS itself.
I’m a longtime Gmail user, but between my BlackBerry and the fact that I don’t get a ton of personal email, I’ve never spent a lot of time working in its web interface. That changed recently when I began piloting Google Apps Premier Edition for me and a couple of other colleague at work – a process I hope to write more about in a future post. But for now, I want to talk about the increase in productivity I’ve seen in the short time I’ve been using Gmail for work, as well as a promising new feature being rolled out today called Priority Inbox.
I've been using Google Chrome since the first beta was released back in the fall of 2008, and it quickly became the default browser on my laptop. For over a…
Yesterday Google announced the release of Google Public DNS, the company’s free domain name resolution service (if you’re unfamiliar with DNS, it’s the system that translates the human-friendly google.com domain to the computer-friendly 18.104.22.168). This news came as a surprise to everyone, and has generated a ton of coverage by technology bloggers and journalists as a result. Unfortunately, lots of it is utter crap, and gets the story all wrong while instead propagating endless fear, uncertainty, and doubt.
By far the biggest news to come out of the Google I/O developer conference held earlier this week was the preview of Google Wave, the company’s concept for the communication/collaboration tool of the future. As put by Lars Rasmussen, one of Wave’s creators, it answers the question: “What would email look like if we set out to invent it today?”
Ever since Google firmly established itself as The One to Beat on the web, the company has become the subject of almost every conceivable product rumor, a surprising number of which either turn out to be true or contain kernels of truth. For example, people speculated for years about Google building an ad-supported “gPhone” mobile phone, when in reality it created an open source mobile operating system called Android for others to use with their hardware.
There were two Google rumors that always seemed too far-fetched to be believable. The first was that Google was creating a complete Linux-based desktop operating system it would give away for free in an effort to poke Microsoft in the eye. While I’ll never underestimate what one company will do to damage a bitter rival, this one seemed very off-mission for the benefits it would produce – just think of all the resources it would take to support such a product.
The other rumor I didn’t believe was that Google was working on its own web browser. While it was more believable than them creating a new operating system, there didn’t seem to be many benefits. Google had a very good relationship with the Mozilla Foundation, basically subsidizing the development of Firefox with ad revenue from the built-in Google search box. And, it could extend both Firefox and Internet Explorer with a variety of plug-ins and extensions, so again, the benefits didn’t seem to outweigh the costs.
As of yesterday, I’m happy to say that I’m wrong about both of those rumors.