I have no idea what you're trying to say. Whatever it is, it changes nothing about the fact that your statement...
I can see that.
...makes absolutely no sense whatsoever. That's all I'm saying.
Let's assume it does not! and I'll just reflect on your list.
- Let's assume we start at your second point which simply puts this first point out of the question.
- Okay, let's assume that Andromeda OS is a thing, otherwise nothing really makes sense at Microsoft, not even the things that we don't assume but know for a fact, such as Windows 10 Lean.
- You could have just bundled yourself CShell and UWP under the name Windows and make sense of my previous statement.
- You could, but it just make no sense to include it in a list.
So basically you have two points made in the above list and that is:
- Andromeda will be distinct of Windows 10.
- Any Windows GUI will be powered by CShell and UWP.
First statement is obviously wrong, since Andromeda consists of the decomposed modules of Windows 10 itself. Or rather Windows 10 as it is to be within 2 years (hence the short-term description of the project) will be the OS composing of the same modules Andromeda has. Andromeda will probably have more modules than what Windows 10 is to be consisting of. You can't be serious about saying that Microsoft is aiming for having to maintain once again two separate OSs, Andromeda and Windows side-by-side without turning Windows 10 into its Andromeda OS itself!
Second statement is almost right. Only you use the term "Windows as whole". You probably came up with this because you simply refuse to accept my terminology; there won't be a "Windows as a whole", but a "Windows". This is exactly what I am saying. You cannot brand an OS as "Windows as a whole". Windows will become a desktop GUI (or a SKU for Andromeda if you will) as you say built up of CShell and UWP. And this was exactly the other thing I just said before. That this SChell UWP will be a simply a GUI for Andromeda that could even be replaced by something else not even making it a Windows, but a Circles, still running Andromeda under the hood.
And when I say Windows will become a GUI, I don't mean the code it is running on obviously, but the meaning "Windows" will cover for Microsoft, and hence the reorg.Obviously you will have different experiences on "Windows" than what you'd have on a thermostat or on a fridge LCD or what-have-you. So it makes good sense to separate these things when decisions are being made in regards to UWP, CShell, some effects, a master-slave UI pattern, a hover effect etc... Windows will not have to deal with whatever changes come by the UWP theme. It will have to focus on having a Tabs experience and a Timeline functionality, as that is what the desktop OS is about. Not Acrylic stuff. Think of it as by decomposing Windows to Andromeda comes with the opportunity and the requirement of distinguishing its functional layers as well. Similar to the way you have 3-5-layer web application design, you will get a better layer-based OS. To this OS, the upper-most layer is what makes it Windows. Not the file-system accessing layer.