Well, David Worthington over at SD Times has struck again, this time with a new piece which describes Microsoft’s planned transition from the current Windows codebase to one based on Midori. From the looks of this, it is definitely not just a research project for Redmond, as Robert Scoble argued after the first piece..

Essentially, Microsoft looks to be favoring a very conservative transition — which would be essentially the opposite of what Apple did with Mac OS X. It’s not surprising considering the massive install base the company needs to worry about. It’s probably smart too: by gradually introducing its customers to Midori it can spot potential problems far before they become major ones.

David suggests three different possible ways Microsoft could introduce the next-gen technology, which I’ve summized below.

The first, and perhaps most complex, has applications that run on both Midori and Windows by following a program model that operates similar to Microsoft Research’s Accelerator project … a second approach to Midori would fork the executive responsibilities and require the development of an executive for Midori that is based on and would run in parallel with the Windows Executive … The most radical suggestion involves writing the proposed Midori Executive itself from scratch, which would transform the bubble into a truly legacy-free platform.

Under the first two, Windows still takes the primary role. Under the last, it is a complete rewrite, which analysts cited by David seem to cozy up to most. I also think this is the best route: if we’re going to make a clean break, make it complete.

David’s working on a piece on security, and I’m thinking that a complete move away from the Windows code if just for the sole reason of security is the best thing. It would send hackers back to the drawing board — having to completely relearn how to hack the OS. Legacy Windows code would be contained, thus damage to systems would be minor, if not negated if I’m not mistaken.

Honestly, (and putting it bluntly), It’s nice to see Microsoft finally growing a set if David is really portraying what the company is saying in its documents correctly.

My former colleague at BetaNews David Worthington has a scoop on the upcoming version of Windows over at his (fairly) new gig at SD Times. David claims that the new operating system, code named “Midori,” is being built completely from scratch and has no relation to the current Windows codebase at all.

This is huge. It essentially equates to an admission by Microsoft that Windows is indeed no longer working. To Microsoft, this project is important enough that Eric Rudder, senior vice president for technical strategy at Microsoft has been put in charge of it.

Midori is said to be internet centric, although it appears that it would attempt to at least support some legacy Windows applications. Such interoperability is almost a necessity as a switch from Windows to another platform would be on a scale infinitely bigger than Apple’s switch from the Mac OS 9 codebase to Mac OS X.

It also looks to take advantage of emerging technologies in computing, according to David’s reporting:

The Midori documents foresee applications running across a multitude of topologies, ranging from client-server and multi-tier deployments to peer-to-peer at the edge, and in the cloud data center. Those topologies form a heterogeneous mesh where capabilities can exist at separate places.

What I’m not clear here yet on is whether or not Microsoft is planning an entire sea-change as far as UI goes — where our perception of what a Windows OS is now is completely thrown out the window. The report seems to suggest in some way that a complete overhaul could be in the cards:

At the presentation layer, Microsoft is making a clean break from the existing Windows GUI model, where applications must update their display on one and only one thread at a time, and the associated problems that affect OS stability and make it more difficult to write multithreaded applications.

The Midori documents indicate that the company has not decided what user interface abstractions are appropriate when applications cut across boundaries, or how to combine the best qualities of rich client applications and Web applications.

Much more can be found in the actual article itself. Now Dave, mind telling me how you got ahold of this document? :)

Follow

Get every new post delivered to your Inbox.