(this is page 62 of 121)





Latest

The elephant in the cloud

The elephant in the cloudThis year at the D conference Michael Dell was asked whether he was worried that the shift towards cloud computing would affect his PC business. Despite not usually seeming like a visionary, Dell gave a great answer. He said that over the last 20 years, every time bandwidth increases, it was his observation that so did the need for processing power on both sides of the pipe, and that because of that, he felt pretty good about the future of his PC business.

Just look at the iPhone or the N95, two mobile phones that pack a tremendous amount of processing power per ounce of weight. Despite being even more suited a a class to offload work to servers in the cloud, smart phones as a category seem to be growing more powerful in their display technology (hardware accelerated video), processing technology (Intel Atom), and general peripherals (5MP cameras, GPSes). Not only are these devices being packed to the gills with more transistors than a mid 1990s PC, but developers are rushing to PC-like development environments like the iPhone's and Google's Android to take advantage of the additional horsepower instead of just writing web applications for the increasingly more powerful web browsers that come with these things.

And it is not just about local processing power; the latest issue of Wired has what will no doubt become a classic piece by Kevin Kelly on the emergent distributed 12-million-teraflop computer that all of our gizmos are getting wired up to make. In the piece, there is a great chart that quantifies the shipped quantities of various different devices with CPUs at their core: from PCs to DVRs, from cellphones to cameras.

Now everyone knows that there are roughly 3 times more cellphones than PCs in the world today, but the stat that I found more interesting is that there are 44 times more PCs out in the wild than servers. Though I realize that it is probably difficult to define what a "server" is in today's world of quad-core x86 machines, the magnitude of that difference brought to mind the delta between storage at the client tier (in offices, in people's homes, at school), and the storage "in the cloud" (i.e., S3).

Even if you assume that the typical x86 server has 13x more storage than the typical PC (a terabyte of addressable storage versus a measly 80GB because you have to factor in the installed base more for the PCs), you are still talking about something on the order of about 100 million petabytes for the client tier and less than a third of that for the cloud tier.

Anyone who has tried to back up a photo collection to a cloud service like .Mac, to say nothing of a music or video collections, knows this at a gut level. The challenges with storage in the client tier have always been consistent addressability and reliability, but in a replicated and distributed world (a la Kelly's megacomputer), we might just be able to make better use of all of those petabytes.

Processing and storage made the PC revolution the juggernaut that it has been. It is why we've come to expect the interactivity native application developers running into the smart phone space are clamoring for, and it's why the dark matter of today's computing environment is composed of billions of hard drives, powered and accessed in a massively distributed way.

It is going to be a while before the cloud catches up with that (datacenter economics and bandwidth being what they are), and until it does, we might all be careful of falling elephants.

Comments Permalink

These paper prototypes of popular websites (via Waxy Links) are absolutely charming. I've always loved drawing paper interfaces because of the way that they help to clarify thinking about what is important. On paper you never have the space (or in my case the skill) to get specific about the details that ultimately don't matter as much as the one or two key actions on each screen.

In fact, I've often wondered why there are no good computer-based prototyping tools— or at least ones that approximate the best qualities of paper. Using Photoshop to prototype interfaces is like using a jackhammer to make ice sculptures; with enough practice you can do it, but there has got to be a better way. Over the years, I've found some tools that help to wireframe (Visio, OmniGraffle), but all of these are still too cumbersome and provide little if any help in terms of interactivity. It is no wonder then that some in the web design community are advocating jumping straight to HTML from paper.

Here is a lazy web idea that might help experience designers: how about a software application that let folks scan in their paper prototypes and then manipulate them with simple drawing/animating tools via point and click. The result would look a lot like Ambrosia's SketchFighter 4000 game (in the best of circumstances) but it would give the prototyper both the speed of initial design that paper provides, and the ability to quickly iterate and animate on the computer. With a few fancy filters, one might even be able to start formalizing the digitized paper prototype by replacing the hand-drawn geometric shapes with real polygons.

Back in the 80s, Dan Bricklin developed "Dan Bricklin's Demo Program" for prototyping text-based applications. Though I've never seen it run, I understand from people that used it that the application developed a cult following among early PC application developers. This scanned paper prototypes application might just fill the same need for the web generation.

Comments Permalink

I love TED talks. If TED wanted to package them up and sell them as a premium cable channel, I would gladly pay for it (and watch more television as a result). One of the best talks I've seen there in recent time is Ben Zander's, "Classical music with shining eyes." Zander, for those that don't know is the conductor of the Boston Philharmonic Orchestra, and a part-time motivational speaker. In this 20 minute presentation, he mainly talks about the power of classical music; however, at some point around the 15 minute mark (don't skip ahead, it is worth it, especially if you like Chopin), he begins talking leadership in a very frank and novel way.

I am not one for "leadership kumbayas—" frankly I find most of that stuff to be a crutch that people use ploddingly and to their organization's great detriment. But to see Zander talk about his key realization as a conductor, to experience him in full story-telling glory, is an experience that stands far above any MBA course I've ever been in. Go invest the 20 minutes!

Comments Permalink

Bill Gates calls it quits

Bill Gates is retiring today. Love him or hate him, everyone agrees that he's had an incredible impact on the technology industry by commoditizing the Intel architecture and driving terrific economies of scale over two decades of the PC's growth. Even those of us on the Mac get to benefit from his plan of putting a computer on every desk.

What is most amazing to me about Gates's career though is how he managed to stay at the helm of Microsoft as it grew from small languages/consulting shop to the world's biggest and most successful software company— all the while remaining very close to the nuts of bolts of the core products. Lots of people tell great stories about his intimate knowledge of all of his company's projects; my favorite tale though is the one Joel Spolsky recently wrote for Inc. Gates's zeroing in on the details of the date functions seems so at odds with almost every senior executive I run into at HP these days. If I had to guess, I say that most of these "implementation details" here are often stuck somewhere between a program manager and an offshore software team and certainly not anywhere near the top of the company.

Bye bye Bill— I'm not quite sure what's going to happen to Microsoft without you (though I'd bet on bad)— but you've had quite a ride!

Comments Permalink

GigaOm had a good review of HP's recent entry into the mini laptop category created by the Eee PC, the HP 2133. I was most intrigued by the premise of the post which was that this new category of laptop should be more than just a shrinky-dink version of a regular laptop, and instead be geared towards "cloud computer" activities.

HP 2133Since I recently got one of these computers to use as a travel PC (to show I can fly the appropriate flag when in customer territory), my interest in this line of thinking was particularly piqued. Here are my thoughts on this notion of the 2133 as a cloud computer:

From a hardware perspective, the HP 2133 miniNote is a wonderful machine, especially given its low price point. It's built like a tank and feels like it could take much more of a beating than my relatively sturdy Macbook Air. Of the 3 HP laptops I've had since having joined the company, it is by far the most "designed" one, and despite whatever anyone says about the Via C7-M chip being JV, it is plenty fast. The screen is really teeny, but it is bright enough and sharp enough. And it's got plenty of ports.

But then there is software. The machine I got runs Windows XP which is snappy enough and stable enough to do real work. However it suffers from two major flaws: 1. it takes too long to boot, sleep, and resume, which in 2008 is sort of like a car without ABS, and 2. it provides zero support for bumping the type size up on applications and the OS at a global level.

Given the tiny screen, this last concern is what may kill the 2133 for you. Even if you have relatively fresh eyes, some of the more text rich applications are almost completely unusable over more than 10-15 minutes at a time (at least without enduring a headache). Outlook 2007 for instance, is just too small to read comfortably. The machine ships with an HP utility that lets you bump up some of the font sizes; however, in my experience it seems to affect only window titles and random dialogs. Maybe the Linux version is better, though I doubt it.

However this is one place where being a "cloud computer" really does help. Because all of the best web apps tend to respect font resizing in the browser correctly, and because Firefox 3 seems to remember when you change the default size the next time you visit the site, Gmail, Google Reader, and an handful of other Web 2.0 apps are really able look great on the machine's diminutive screen— quite usable in fact when paired with the machine's awesome keyboard. It was surprising to see web apps beating the native client— at least until you stop to think that the machine is running an 8 year old OS!

I don't know that I'm quite ready to give up the Air for the 2133, but I could definitely see using it for a subset of limited "cloud like" tasks.

Comments Permalink