Debating time slot has passed. No more time. Microsoft has only 3 ways out, a.k.a. “3 options” :
- OLD — new Win releases backward compatible with OLD
- NEW — totaly new Win not compatible with OLD
- OLD + NEW — New WIN , not backward compatible
- But with limited time life and support of OLD Win .
I think only “Option 3” is viable strategic way forward for Microsoft. Old Win version may run exclusively as virtual machines on top of “Option 3” (N.S.) In the “transition period” until all the key apps are ported to “Option 3”: Office, Visual Studio, SQL SVR, etc …
Before anyone else, I would also like to suggest a new part of the MSFT group : OPTION3.MICROSOFT.COM. Director position to be filled by Me, of course ;o) Thus I am not obliged to describe my navigation into new “Option 3” territory. Aka the Strategy.
As soon as WINDOWS OPTION3, reaches “customer shipment” stage, all the previous MSFT OS-es, to be made free. All legacy server OS-es to be also free, with “maintenance costs remodeled”.
WINDOWS OPTION3 OS price : 50 USD.
There is no desktop/server version, because everything is 100% modular.
50 USD buys the OPTION 3 CORE. All the other OS modules are free. This is so called “system set” , made by MSFT, and not documented. All the other module set’s are third party. Free or not, that is to be decided by the producers. Office Option 3 will be just set of modules in this OS.
Option 3 module is NOT what we call today an “Application”. Windows Option 3 OS is set of Option 3 OS modules + set of App’s specific modules built by App’s vendor. … Option 3 module architecture is an stand alone executable (out of proc). Very much something like out of proc DCOM exe is today.
Fifth decree: Option 3 OS subsystem is set of Option 3 OS modules. Example: Option 3 CLR is made up of several Option 3 modules.
Term “component” is abused in the past and as a such not used in the Option 3 vocabulary
System language of Option 3 OS is ++C. This is C++ but without any C legacy inside, whatsoever. Intrinsic types are abolished. Compilation units are abolished, global namespace, etc … All the fundamental types are classes, including pointers. there is no single common root class. Of course there is no GC too. Imagine C++20 with no C support.
More decrees to come soon …
Update 2009, May
I was right and obviously Microsoft has read this blog post and implemented what I advised 🙂
They have introduced VirtualXP for Windows 7 ! Exactly what I suggested in June 2008.
Legacy to be dealt with using point 1 from above. They have implemented it (1) as a virtual PC variant which gives transparent virtual hosting for WIN XP PRO SP3 applications installed and running inside (2) Windows 7.
Although Windows Option 3. Might never happen.