The Network is NOT the Computer?

A hurdy-gurdie at the Victoria and Albert Museum in London.

I’ve recently attended Microsoft's launch of their 2008 suite of products, including Visual Studio. It was held in a movie theatre where there were two presentation streams, one for IT Professionals and one for Developers. I attended the developer stream. Very little PowerPoint and lots of live demos with code snippets being included in the examples. Visual Studio now supports Javascript as a first class citizen. This drew applause. I guess it was a sorely needed gap in IDE’s. I wonder if Javascript will become (more) fragmented as a result.

The integration of desktop presentation with the network, with attendant DRM-enforcing security as well as extensions to browser functionality is overwhelming and integration of desktop with network apps is almost complete; they are ready to link their OS and .Net environments to Internet content in a seamless way - the network is NOT the computer was the loud subtext. In fact they have made it possible to decouple the presentation layer of an application from the server side so that it works either through a client-server virtual desktop (think Citrix-like), through a regular-looking window, or through a browser.

This is resistance to the Google model, where the client is as thin as possible and standards are used as they should be. The gamble with the MS approach is that users will be sufficiently attracted to the extra features of a tighter integration to the desktop to pay money for it. Makes sense given the business model.

There were also a few intro videos at the start of the various sessions, and the most humorous included a therapist and his patient discussing the relationship between a developer, his machine, the tools and the operating system. Here, the unstated subtext was that colourful computer cases, slick hardware design etc were no match for technical flexibility and ego-boosting developer learning curves (a jibe at Apple I guess). Shakespeare wrote that wisdom comes alone through suffering, which may explain why hazing works to bind a group, and may explain why people who adopt product lines like IBM’s and Microsoft’s end up defending them so strongly. I think it is a case of confusing the side effect with the cause.