Commentary

Chris Murphy
Editor, InformationWeek  

Desktops Irrelevant? Oh, That It Could Be So

SiliconRepublic quotes a Google Europe exec saying "desktops will be irrelevant in three years." CIOs can only dream that some device, any device, would actually go away.

SiliconRepublic quotes a Google Europe exec saying "desktops will be irrelevant in three years." CIOs can only dream that some device, any device, would actually go away.Here's the background, from SiliconRepublic.com coverage of John Herlihy, Google VP of global ad operations:

Speaking at the Digital Landscapes conference at UCD, Herlihy said that the cloud-computing opportunity will make sure that every mobile device will be capable of doing rapid-scale applications.

"In three years time, desktops will be irrelevant. In Japan, most research is done today on smart phones, not PCs," Herlihy told a baffled audience, echoing comments by Google CEO Eric Schmidt at the recent GSM Association Mobile World Congress 2010 that everything the company will do going forward will be via a mobile lens, centering on the cloud, computing and connectivity.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

I suspect this reflects more Google's consumer's eye view of the world than of business computing. Even for business, though, it's correct in the broad sense that we'll use fewer big, honkin' machines wired to a desk, and mobility will be prized.

But most CIOs don't have the luxury of writing off any form factor, including the desktop, even as they prepare for a massive proliferation of new devices. They understand what Herlihy's getting at--that employees, just like tech consumers, will demand mobile computing. Smartphones will get more powerful and common. Places such as General Motors and Ford are in the thick of programs to let employees use their personal smartphones for work e-mail.

Yet CIOs also still have engineers using CAD systems, statisticians doing data visualizations, call center reps using real or virtual desktops, and any number of other uses that don't lend themselves to laptops, let alone netbooks or smartphones. It's actually one reason to enable work access via personal devices--employees want and need some mobile access, but companies don't want to mobilize everyone's total work experience. So give them just the e-mail slice on their smartphone.

Instead of thinking of "desktop" as a machine, CIOs must think of "desktop" as a result: giving employees access to their files, mail, workflows, and the like, often regardless of the device.

So if in three years, someone calls up a work environment on a iPhone, checks e-mail, then plugs the phone into a big monitor and keyboard to make some Excel refinements, then sends the results to a SharePoint repository, and her traveling colleague uses a Google Chrome netbook to check the changes, while another in the office uses a full-sized notebook, and another uses a home PC … is the desktop dead? No, the CIO's challenge has just spread over many more devices.

Mobility is the very real challenge. The notion that its kills the desktop is wishful thinking for most CIOs.

Related coverage: Global CIO: UPS Provides Peek Into Future Of Wireless Google Chrome OS Coming. Got A Netbook Strategy? Global CIO: Fear Of Facebook For The Enterprise Global CIO: Will Google Miss Its Moment In Enterprise IT?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links