What is the use-case for this? Modern Linux distros have all the tooling, libraries, utilities already - is the idea to use this for hosting .Net stuff?
I think the point is that "Windows" is pretty thin with this server. If there's no GUI available that sounds like there will be no USER32 (good riddance btw); and if there's no USER32, many "Windows" programs won't work.
Well obviously - this just seems to be creeping into the space where Linux is an incumbent anyway and I can't see anyone who's running common OSS stacks wanting to use this in favor of Linux based platforms.
If you have servers that need to run Windows, even if they can't run on Nano, you can have fat Windows Server boxes and Nano boxes and configure them using the same tools, rather than having a mixed Windows/Linux shop?
With micro service architecture being one of the big buzz words at the moment, I see this as a great way to separate individual micro services (with some clever routing in front). Using Nano would make these services separate and easy to update without affecting eachother. Continous delivery FTW :-)
