Microsoft in Reality — a look at the latest memos from Gates and Ozzie
Big things happen at Microsoft and in the marketplace after Bill Gates announces a grand strategy. Ten years ago this coming Pearl Harbor Day, Chairman Bill famously made a speech challenging his company and his opponents to take advantage of the "Internet Tidal Wave" that was the subject of an equally famous memo the prior May.
The first time around, the headlines cast Microsoft's challenge in strictly competitive terms. The great "threats" to Microsoft back then were Netscape and its browser. This time around, it's clear that The Net is The Environment, and that what matters in that environment are services. Here's Bill:
We must reflect upon what and for whom we are building, how best to deliver new functionality given the internet services model, what kind of a platform in this new context might enable partners to build great profitable businesses, and how our applications might be reshaped to create service-enabled experiences uniquely compelling to both users and businesses alike.
The italics are mine. That phrase internet services model stuck out for me, because I had heard it first from Craig Burton back in February 2001:
I have developed a model for measuring the progress of the computing industry from an Internet Services perspective. This perspective is the Internet Services Model (ISM). This model is not limited to a services technology conversation, but also includes a lexicon to discuss the model....
Before getting too much into the vision of the Internet Operating System, it is useful to cover the nature of the infrastructure business. The infrastructure business is an enigma. This is because it is built around an interesting paradox. I refer to this as "The Infrastructure Paradox."
Vendors of infrastructure have two prime objectives:
- Generate shareholder value.
- Foster infrastructure ubiquity.
Each of these prime objectives is in direct opposition to each other. The extreme of generating shareholder value would sacrifice infrastructure ubiquity. The extreme of fostering infrastructure ubiquity would sacrifice shareholder value. Without getting too "Zen" in the matter, the trick of success is to constantly balance the two prime objectives.
It is completely possible to at once generate shareholder value and to foster infrastructure ubiquity. (More on this later.) In the current state, the industry is out of balance with these objectives. This is because the key to balancing the objectives is innovation. There is currently a major infrastructure growth deterrent keeping the entire industry out of balance, or in darkness; a state of Web Noir.
His Web Noir piece is damn interesting too, considering the fact that it was written nearly five years ago.
It should be clear by now that the Net's infrastructure what Craig calls the Internet Operating System is NEA: something Nobody Owns, Everybody can use and Anybody can improve. Its end-to-end architecture is one Craig compares to a hollow sphere: a world of ends wrapped around a three-dimensional zero.
But that doesn't stop Microsoft, or anybody, from wanting to own it. It does, however, stop them from actually owning the Net's infrastructure itself, which is too deep and too free (as in both beer and speech). Craig's outline of the Internet Services Model shows the playing field in a layered diagram that distinguishes between network and application services.
Money will be made at the latter, far more than the former.
The question becomes, "Where's the silo?"
Now that everything is being built by everybody with fewer and fewer dependencies on any one vendor as a sole source of technology, it will be harder and harder to build silos for people and companies that are losing their willingness to live in them.
Which is why I see this whole thing as an adjustment of Microsoft to reality, rather than a call by Microsoft for the reverse.
Doc Searls is Senior Editor of Linux Journal
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- August 2015 Issue of Linux Journal: Programming
- Django Models and Migrations
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Huge Package Overhaul for Debian and Ubuntu
- Shashlik - a Tasty New Android Simulator
- KDE Reveals Plasma Mobile
- Embed Linux in Monitoring and Control Systems
- diff -u: What's New in Kernel Development