news - leaked info on microsofts new os Midori

**Jason28** · 06-08-2008 12:08 AM

windows will be replaced with a secret operating system in the not so distant future. rumor has it there rushing windows 7 it will now be available in the first half of 2009 instead of jan 2010. this new operating system microsoft is currently working on has the codename Midori we all know this will not be the final name. this os is completely new nothing like windows altho details are minimal all i found out was its better than windows 7. it will break the practice of software physically being installed and instead become a virtual portable operating system.

edit: some more features from microsoft watch:

Virtualization. Microsoft isn't giving up on backward compatibility but doing what I've been asking for since the company bought Connectix in 2003: using virtualization to provide backward compatibility between a new operating system architecture and an older one. Unfortunately, David won't reveal how Microsoft will use virtualization for the Windows-to-Midori migration until his second story. But I commend the concept. Microsoft has the technology to make it all work.
Modularity. "Unlike Windows, Microsoft intends for Midori to be componentized from the beginning." Finally! Microsoft moved down the modularity path with Windows Embedded, ending, so far, with Windows Server 2008. The current marketplace demands modularity, for lots of reasons. Among them:

Providing a single, secure, manageable operating system for all devices
Scaling across multiple devices and SOAs (service-oriented architectures)
Writing software once, rather than porting different versions to different devices, platforms or service topologies

Simply stated: Modularity is one of Midori's most important design principles. None of the other design principles effectively work without the modular, or what Microsoft calls componentized, approach.
Connectivity. Midori shares a common goal with the first real version of Windows, NT. But the scale dramatically differs. Microsoft designed Windows NT to be connected across corporate networks. That connectivity would later pose some security challenges as corporate networks connected to the Internet. Midori is much more about connectivity, regardless of device or even underlying architecture. Midori is designed to live on the Internet, to be connected.
There's something agnostic and not (more on the not in the closing paragraphs) about Midori, at least the conception revealed by SDTimes. David writes:

Midori will be built with an asynchronous-only architecture that is built for task concurrency and parallel use of local and distributed resources, with a distributed component-based and data-driven application model, and dynamic management of power and other resources. Midori's design treats concurrency as a core principle.

He continues:

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.

Conceptually, the approach is very forward-thinking and anticipates distributed, cloud and services-oriented computing demands that already tax the PC client-server model. The leaked documents repeatedly refer to the importance of "concurrency," according to SDTimes. "Midori will have provisions for distributed concurrency—or cloud computing—where application components exist in data centers."
Whoa. But, damn, it's ambitious, too. Microsoft projects Cairo and WinFS both failed, and their data storage models would have brought some of these same capabilities. Concurrency and connectivity are sensible topologies. But can Microsoft really deliver them? There are reasons why Midori is still an incubation project.
Device support. Midori's connected and concurrent topologies directly relate to hardware devices. David explains:

Users move across multiple devices, consume and share resources remotely, and the applications that they use are a composite of local and remote components and services. To that end, Midori will focus on concurrency, both for distributed applications and local ones.

I won't separately call out synchronization, but incorporate here. What the above quote really means: Microsoft's concurrency topology would make personal or professional information available everywhere people need it. The seeds of this concept can already be seen in Live Mesh. Data changed on support device A replicates elsewhere.
If that's so, I have to ask: How many of the Midori concepts are already part of Microsoft's forthcoming services platform? And how different are they? David's leaked information about Midori reads very much like what I would also expect from Microsoft's SOA. If they're not one and the same, then Midori may be more than a Windows successor by a future iteration of Microsoft's SOA platform.
Services architecture. I'm throwing this one in as an extra because it's potentially troubling or exciting depending on perspective. David writes: "Midori's applications would be created using .NET languages that will be compiled to native code using the [Only registered and activated users can see links. ] compiler and runtime system, which is presently a Microsoft Search project."
Midori would embody a .NET-language-based "type-safe abstraction set" that "will eliminate an entire class of programming errors that stem from bad pointer arithmetic, enable the changing of the boundaries between privileged and unprivileged code, and provide for universal application analysis and instrumentation, Microsoft reasons."
For some developers, the approach could mean cleaner code more easily written. But the architecture means something else: Microsoft would more deeply bake .NET into the operating system architecture and extend it to many more devices and services. If I read this rightly, .NET literally becomes the Net, from a development perspective. Such an approach would make Microsoft's bundling the browser into Windows—an act that drew a U.S. government antitrust lawsuit—seemingly inconsequential. Midori's .NET bundling would reach across a vast Internet landscape of devices, development topologies and SOAs. To repeat: .NET would become the Net.