Joho the Blogcloud Archives - Joho the Blog

October 31, 2011

The Firefox difference

Sebastian Anthony points to a distinguishing philosophy of Firefox that was not clear to me until I read it. The title is “Firefox is the cloud’s biggest enemy,” which he in the comments admits is not entirely apt. Rather, Firefox wants you to own and control your data; it uses the cloud, but encrypts your data when it does. This is a strong differentiation from Google Chrome and Microsoft IE.

Comments Off on The Firefox difference

June 9, 2011

iCloud vs. Google’s cloud

This MG Siegler TechCrunch article really clarified Apple’s strategy for me. It makes much more sense here than I was getting from the coverage of Job’s talk. For example, it let me see the connection between the new Lion auto-incremental-save feature (which sounds incredibly useful on its own — I currently use ForeverSave to accomplish much the same) and iCloud: your applications will save invisibly, and will save to an invisible place.

Google’s mental model makes more sense to me: You should understand that you are saving your stuff to somewhere, rather than just have the confidence that they will show up on whatever set of devices you’re using. But my mental models for computing were formed back when computers were computers, not slates of glass that directly respond to the movement of your fingers as if the glass was skin. For those who think of laptops as iPads with non-removable keyboards, Apple’s strategy makes more sense. And the iPad generation is going to win simply by being smart enough to have been born later than me and my laptop buddies.


February 24, 2011

Google Chrome: The OS, the laptop, the browser

Klint Finley at ReadWriteWeb writes:

Google is bringing Web apps one step closer to having full desktop functionality. Today, it announced new functionality that allows apps from the Chrome Web Store to run in the background, even when all Chrome windows have been closed but the user hasn’t actually exited the browser. Why would you want to do this? A couple of reasons.

1. To enable hosted apps, such as calendars, to provide notifications without having to leave a window or tab open for the app.

2. To enable apps to load content in the background so that it’s instantly available when a user launches the app. For example, a dashboard with real-time information, or something like that takes a while to update.

This brings Chrome the Browser one step closer to Chrome the OS … and if I were Google, I would not go much further than that. At least for now.

I say this as the recipient of one of the tens of thousands of CR-48 Chrome notebooks Google sent out over the past couple of months. (I strongly suspect it was sent to me by someone at Google Docs, because I spent a morning with them about a year ago talking about next steps for the product. It was an unpaid session [well, until now], and, as far as I can tell, what I said had no effect. Very interesting morning, though, from my point of view.)

The Chrome netbook comes with an early version of Google’s Chrome operating system installed. As many have pointed out, the hardware is a mix of pretty nice and totally sucks. The point of the distribution was not the hardware, but, rather, how well the OS works. Nevertheless, let me get the hardware comments out of the way. Positives: Fairly lightweight for a screen that large. Good battery life. It was free. Negatives: OMG the trackpad is frustratingly awful. The lettering on the keyboard is invisible except in full light. The mouse tracking speed cannot be slowed down enough. And because there is only one USB port, you can’t easily plug in both a mouse and a USB lamp to light the illegible keyboard. Anyway…

The key difference apparent to the user is that the Chrome OS is a fullscreen browser with no desktop underneath it. Everything is optimized for online work. That’s great for online work: The wifi connection is easy, setup overall was easy, it’s getting very good battery life even though wifi is on all the time, it starts up lightning fast, and it actually both goes to sleep and wakes up instantly when you close the lid. So, when you’re online, Chrome is terrific.

But I am not always online, and even when I am, I often want to use local apps. For example, there are some good text editors online, but they are not better than the copy of TextWrangler I have installed on my laptop. Furthermore, Google Docs has its strengths, but Pages, OpenOffice, LibreOffice, and even Word all are better at some important things. Much better. Why does it help me as a user not to be able to use the apps I want? Plus, I have many years of documents and other data on my computer (yes, multiply backed up); I’d have to move them all into the cloud to have them at my fingertips when using Chrome. But why would I want to go to all that trouble…except to use Chrome?

Chrome is like a visitor from the future when wireless connectivity is ubiquitous, but the available apps have been frozen since 1996. It is in that regard the worst of both time zones. Sure, the apps in the cloud will get better, but I am unconvinced that there will never ever be any app that I want to run locally. In the meantime, I’ve taken to using my CR-48 as the laptop I keep on our TV couch, so I can figure out where I’ve seen that actor before, which I suspect is less than Google hopes we’ll be doing with their shiny new operating system.

On the other hand, enabling Chrome the Browser to permit Web apps to work in the background is a brilliant idea for the here-and-now. We can continue to use our highly-evolved local apps, but still integrate cloud-based computing into the world we’re going to be in until creatures from the future blanket our land with wireless, open, broadband access to the Internet, or until our government comes up with policies to do so. (My money is on creatures from the future getting here first.)

[But, hey, Google, thanks for the free laptop, and I do admire your willingness to push the envelope.]


February 7, 2010

Cloud capitalism’s threat to cloud culture

Charlie Leadbeater has a terrific post on the threats posed by the fact that The Cloud (as in “cloud computing”) too often actually is a recentralizing of the Net by profit-seeking companies.

The easiest example cited by Charlie is Google Books, which provides a tremendous service but at the social cost of giving a single company control over America’s digital library. The problem here isn’t capitalism but monopolization; an open market in which other organizations could (the pragmatic “could,” not the legal or science fiction “could”) also offer access to scanned libraries would create a cloud of books not solely controlled by any single company. (The Google Books settlement threatens to rule out competition because without an equivalent agreement with publishers and authors, any other organization that scans and provides access to books runs the strong risk of being sued for copyright infringement, especially when it comes to books whose copyright holders are hard to find. The revision of the Settlement is less egregiously monopolistic.)