I love technology, and can’t help myself when it comes to trying out new services and dissecting new gear into the tiniest spec-sheet detail. Most of the time I do this only out of love for technology. Trying out a super unstable alpha or beta of a new service or app is for example usually a huge hassle, with frequent crashes and misery. Google Wave was one such example. When I first laid my hands on one of the Wave sandbox accounts back in July of this year, the thing was just a mess. It crashed all the time and was rather useless. Still, I loved playin with it, just for the sake of the amazing ambition and engineering behind it.
Recently, I started running Wave on my iPhone and natively on OSX (well, not really natively, it’s Gears-powered) via Waveboard. It’s crude, but is sort of works. Running Wave on the iPhone may not be super useful yet, but absolutely necessary if they want it to replace email of course. Or replace any means of communication for that matter. Mobile is not mobile anymore, it’s just a compromise between interface and size in a computer.
But here comes the surprise: A couple of weeks ago, I got my hands on an early alpha version of Google’s browser Chrome for OSX. I expected a horrible unstable shell of a browser, but perhaps some interesting indications of what Chrome will offer us when the first real versions are released. I fired up Chrome and started playing with it. This thing was fast. It was running really smoothly. It was stable. After a while I started using it more and more for all kinds of things, even though it apparently sucks privacy-wise, and Google advices against using it as a browser yet. Despite these flaws and others, such as buggy printing, I can’t help myself. The user experience compared to all other OSX-browsers I’ve tried it just so much snappier. I use it all the time. Can’t wait for a sharp version of this thing.
{ 0 comments… add one now }