a5cent
New member
- Nov 3, 2011
- 6,622
- 0
- 0
I agree with all your points except two:I don't think anyone is going to buy a Windows Phone and be disappointed that it doesn't have IIS.
1)
You're taking my remark about IIS slightly out of context.
The point of mentioning IIS was to counter the FUD in regard to Win32 being the "only" part of W10 that W10M omits. Nothing more, nothing less. Those who know what IIS is aren't likely to be confused by any of this :wink:
2)
At this point in this thread, the only argument left to defend calling both OSes by the same name is: "it causes no harm and people won't be confused".
Well, that claim has already been proven false many times over in these very forums. Last time MS called both OSes just W10 I was regularly explaining to people: "no, your future W10 phone won't run desktop software so don't worry about how awkward that will be without a mouse".
Sure, we can educate and correct people until the cows come home, but is that really the mark of a good marketing message? Something that forces us to repeatedly explain what a product can't do?
Oh yeah, and just wait until the x86 phones running actual (full W10) are released. Then we can start explaining how some W10 devices can run W10 desktop software while other W10 devices can't. Nope... not confusing to the layman at all /s :wink:
There's got to be a better way to market these devices and the innovations surrounding MS' shared UWP that doesn't distort technical reality to this extent.
