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
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide