Many (including me) feel that this is just the start of a new EEE cycle by a panicked Microsoft, and will be killed off by Microsoft once they managed to reverse their current downward trend – just like other supposedly community-/interoperability friendly projects before, e.g. this project's direct predecessor SFU.
I feel like this seems like a way more developed strategy for keeping developers engaged... dotnet going open source and multiplatform is a pretty big gesture for just a downward trend thing.
No, that's not what embrace-extend-extinguish is about. The worry about EEE is that they establish dominance through vertical integration, introduce incompatibilities through both incompetence (bugs) and malicious behaviour (features), which will weaken and destroy the free standard implementations.
I'm not worried though. This is a neat hack, and may be useful for some people who for whatever personal reason won't switch to Linux proper, but it will not gain anything like the dominance required to push through incompatibilities. Unix applications already deal with a heterogenous environment, to say the least, and Winux will just be one more participant; not a particularly important one at that.
Everyone migrates, draining valuable developer resources from projects like cygwin, mingw and colinux and others. When Microsoft kills it, they will have killed off not only their project, but also the community projects that could replace it.
Meanwhile, because the NT kernel has vastly different performance characteristics (e.g., bad forking performance), we're going to see an increase of "Linux/NT" optimized software that will perform poorly on native Linux kernels, pressuring more developers (and ops) to buy into Microsoft's effectively proprietary solution, completing a vendor lock-in that will continue to bleed the industry long after it stopped being beneficial (see also, every other instance of vendor lock-in ever).
