Well at that rate, unless perpetual enterprise licenses are a thing it looks like its back to Windows 7/8. There is almost nothing that exclusively requires Windows 10 anyway. Even DirectX 12 is only supported by a handful of things.
I guess a person could use their router to block Microsoft IP addresses between certain hours. Mine has this ability.
Linux Mint user on Desktop, Ubuntu on server. I run a VM for the very few Windows things I need. If Ii need to do Video editing I use KDenlive, which is close to Sony Vegas (which I used to use on Windows for Video Editing). Gaming is an issue, I’ll admit, I don’t game anymore due to losing the passion for it after working for Blizzard (not the job’s fault or Blizzard), so it’s not an issue.
My Toolchain for Printing is FreeCAD > S3D > Octoprint running on an HTPC running Ubuntu.
I see why a lot of people use Windows, for me though after working as a SysEng for years and working with M$ products server-side, I just find being a Linux specialist all the Microsoft stuff to be convoluted and arse-backwards.
@Ax_Smith-Laffin , I totally want to say: “It wasn’t Blizzard’s fault, IT WAS ACTIVISION!!”
Because Blizzard really took a shit when Activision took them over. 
Likewise…I know an Microsoft certified network engineer; He works for Microsoft. Managing their Linux servers.
A little registry editing will cure Win10 auto-reboots. First link also requires changing permissions on a task scheduler file so the updates cannot write a new schedule.
and
Linux. Absolutely Linux. Right now I have more issues running Repetier Host on Windows (WITH a proper VM for that stupid UI) than on Linux with the hacked up Mono support.
Mono sucks.
@NathanielStenzel I agree, but it still works better than Windows! Hahaha… Three years of printing, and zero unwanted reboots, but I still have “auto” (“apt-get update -y && apt-get upgrade -y” in cron job) updating on!
@NathanielStenzel Why does mono suck?
@William_L_DeRieux_IV It is more of a personal experiences thing, I guess. I use it from Linux. That implementation was described as a hack by someone else. I think I looked into it once and did not like how it was put together, but it was a ways ago and I do not remember the details. Slic3r was always giving me trouble because Mono got stuck.
@NathanielStenzel I have never used mono in regards to 3d-printing (or have used 3d-printers at all), but right now Mono seems to work on Debian just as well as it did on Windows with .Net (now if something was bugged in Windows .Net – there’s a good chance it is bugged in Mono, too…they have to keep it that way for compatibility).
Also, mono had been heavily updated (the stable mono runtime on Debian is v3.2.8 with v4.6.1.3 in testing/unstable) with the testing version support has been added for .Net 4.5/4.6 and monodevelop has been updated to support them as well.
I have several programs that I have written (and several others that I have not) that all work on Debian flawlessly – granted some of the code needed to be updated for cross-platform support, but that was mostly due to directory separators, registry access, and most uses of any win32 specific api).
In other words, in it’s current state, mono is far from being just a “hack”.
Also it works on my machine for Repetier Host. I even have the “wrong version” warning from Repetier Host and it still works better than Repetier on my Windows machine!!