A Google OS?
Readers of this publication will understand that Google is not literally going to go into the operating-systems business, challenging Microsoft on its own turf by selling—how, exactly?—a competitor to Windows. But taking over some of the more visible functions of a desktop operating system is something else again. The existence of Google Desktop pretty much indicates that Google doesn't think there's anything crazy about that idea.
But the desktop is simply not Google's turf, the Web is. Anything Google invests time and money in is going to be tied to the Web. And so we see developments like the rumored Gdrive, Google's Oregon server farm, and its purchase of massive amounts of dot-com-era dark fiber. Whatever else these developments mean, they show that Google is looking at all the different ways it can be involved in computer users' connection with the Internet.
So, again, how do you ensure that you're up on what it takes to play smart with Google? Along with the aforementioned tools, consider looking at Google Web Toolkit, which lets you build AJAX apps in Java.
The Great and Powerful Ozzie
Microsoft is a programmer's company. They will give you the APIs, the software roadmap, the hands-on workshops, they'll work hard to get you to work with them and develop with their tools and for their platforms. They may not tell you everything, but Microsoft gets it that they must communicate with developers.
But they have to know what the message is. When a company gets to a certain size, it can be totally sincere and open about pushing in two diametrically opposed directions at the same time. Look at IBM up until a few years ago.
And then there's the little matter of Gates stepping down.
Without taking anything away from the Myhrvolds and Simonyis and other technological visionaries Microsoft has employed, there is no doubt that Microsoft has looked to Bill Gates for its technological vision for 30 years. And the very fact of the care with which he's making his departure leaves little doubt that Gates is really removing himself from that role. This will have consequences.
There is already evidence that things are not all sweetness and light inside Microsoft: One Ballmer protégé recently left the company in a manner that revealed cracks in the usually smooth wall of corporate imagery. And while Steve Ballmer is a strong and effective executive, this is a technology company, and the departure of the technology leader creates a power vacuum. Ray Ozzie will have two years to establish himself and fill that vacuum, and he will presumably have Bill's support legitimizing him during all that time, so it won't be as chaotic as it could be.
Also, Gates has been doing everything he can to turn this ocean liner before leaving the bridge. The movement to the Web is happening. Some things are clearly established. Microsoft will continue to be a desktop operating system company, will continue to be a tools company, will continue to be an application software company, and will continue to be a web destination. Beyond that? Well, for web services you might want to make sure you're up to speed on WS enhancements, the .NET Framework 2.0 SDK, Windows Communication Foundation (Indigo), Visual Web Developer...But you already knew that. The more challenging task, and just as important to many developers' futures, is observing Microsoft to see if it will hold onto its power position in the industry.
