I do development using a Hyper-V guest with Server 2016 (and 2012R2). These Virtual Machines (VMs) are hosted on Windows 10 Professional. This is a requirement for SharePoint development. This is desirable for web-based development to work in a similar environment that will host these applications (even if hosted in Azure). Windows 10 is too far removed.
So when Microsoft released Server 2016 without UWP or Microsoft Store support, that was bit of a surprise. That meant no Edge browser support, so we cannot test our applications against their premiere browser. We cannot develop and test UWP applications. So we don’t support them.
Microsoft Windows Server 1709 is Server 2016 on Build 1709 but without an GUI. So that isn’t very useful for running Visual Studio. That means our developers (myself included) are using Server 2016 Build 1607 because we need a GUI for our development tools. This means we can’t take advantage of 1709 features available in Windows 10. This includes OneDrive Files On-Demand. Why is this feature so OS-specific anyway? It should be a product feature that we can install anywhere. This makes no sense.
So they have created a set of really inconsistent platforms (read: fractured) and confusion with developers on how best to support various platforms. Or not support them because it is too hard for us. Developers help make the platform because the ecosystem cannot survive without them.
I will take a look at moving to Windows 10 Pro VMs as a development platform. Maybe that is the way to go, with the exception of SharePoint development (unless such can be done with the upcoming SharePoint 2019). In years past, it was too painful to do DevOps on a desktop OS while supporting a server OS. That is why we developed on server OSes. Time will tell.