Besides, in a sense, Microsoft did this when they moved the desktop product line to NT. It wsa a similar compatibility break and a similar improvement in stability and switch to a robust, multiuser, preemptively-multitasking kernel as classic Mac OS to XNU; it's just that the kernel Microsoft already had in house was NT, and the one Apple/NeXT had was XNU.
After a couple years, they could make Windows server run on a Linux core, and then another couple years have Windows run on Linux.
The whole progression could be pretty smooth, covering several years and taking a milestone-driven approach.
With the surface, im sure hey could use that to their advantage and have kore control over hardware.
Perhaps the best impetus to do this would be if they ever really wanted to migrate to ARM and reduce their reliance on the intel platform.
The hardware piece is important, but definitely controllable. Just like you mentioned NT, but this time with a smaller set of vendors to work with.
Nadella is a smart guy and has moved MSFT in the right direction. If his truly makes sense, then he’ll probably do it.
I'm not a .NET dev currently running PopOs on my XPS 13. VS Code is my primary editor for all things. If MS released a desktop that looked this good and came batteries included for their tool chains and services I'd hop in a heart beat.
My only guess is that doing so would lower consumer confidence in the corporate space? I know Chrome books are making a push there and the psychological factor of "it's not Windows" does seem to be a competitive advantage for MS (for now).
Microsoft was apparently one of the candidates that was in talks to buy Red Hat.
https://www.businessinsider.com/red-hat-deal-talks-with-amaz...
According to the article, they eventually dropped out because of anti-trust concerns.
So yes, giving up entirely on the good things that Windows does without respect to the GUI and accepting the practices of Linux/Unix devs who have little or no respect for the past would be nothing short of a catastrophic mistake. Your idea would likely have killed computing forever, in my view, especially enterprise or professional-use computing, and within the first two rapid releases that broke necessary functions. It's the so-called 'Softies' who keep the world running and effective for normal people who don't want to have to figure out how to compile a program just to turn on their computer and do the things they need.
And it would have killed home use as well - we don't need network workstations at home with limited control, we need computers that we have full control over, all the time.
looks at the state of desktop computing
..and yet, here we are.
I'm afraid you have to realize you're in the tail end of the tech adoption cycle[1], either in the late majority or bordering on laggard.
Also, I've never updated Android OS on a device - every phone and/or tablet I have, has the version of Android it shipped with; whatever that might be. The same goes for iOS, mostly. My old iPad, I knew better than to update the OS. The newer one, I've made the big mistake of upgrading to iOS 12. I'm sorely tempted at the moment to make a list of programs on the device and reset it to get it back to decency.
My feeling is, people are allowing the tech companies to release buggy software, they're still buying it, they're still paying for hardware using it and supporting bug-ridden versions. We need to shift the mainstream - and the business world - back to demanding software that works and keeps on working reliably for the life of the business.
If/When you discover a bug, and the developer has a fix out as a security update -- eg heartbleed -- then would you really not update because you trusted that developer before. Surely that they've issued a patch that they suggest to apply means, if you trust them, that you should apply the patch?
Maybe some Linux devs, but many Unix devs have been around a long time and are pretty insistent on backwards compatibility too. ;)
But otherwise UNIX's compatibility story is pretty damned atrocious because part of its culture is relying on everybody to recompile everything.
Which Unix's had this "pretty damned atrocious" backwards compatibility approach?
My experience across Solaris and Linux has led me to believe it's also been a strong nix thing too, not just a Windows approach. I used to use FreeBSD a lot too, but that was years ago and I don't have clear memories of it's compatibility approach. :/
Which nix's are you thinking of, which don't offer strong backwards compatibility for compiled binaries?
Afaik pure DOS mode wasn't in Win2000 and XP, and it uses virtualization or something like it.
Given that, maybe it would also be possible to implement a compatibility layer so some amount of current Windows drivers could be used anyway. I don't know if that's feasible, but if it is they're in a position to pull it off.
But, to avoid alienating their huge existing developer community, they would first do well to get behind Mono [0] and maybe even, make it official (edit: Mono is "Sponsored by Microsoft", so already quite official indeed). In fact, as of 2014, there have been very promising signs in that direction. [1]
[0] https://www.mono-project.com/
[1] https://opensource.com/business/14/11/microsoft-dot-net-empo...
So, put the Win10 GUI on a Linux desktop?
As the saying goes "Now you have two problems". :)
This had the advantage that the underlying OS base would no longer need maintaining by Microsoft, and all their coding efforts could be allocated to the Windows GUI, thus permitting Windows versions to be released far more often than every 5 years as was the case back then.
Being full of Softies, the crowd on Mini-Microsoft dismissed my suggestion out of hand, it being sacrilege of course to even think of marrying the 'upstart' Linux with the 'sacred' Windows code.
Naturally, today I am smiling to myself that MSFT could have taken my idea and run with it, but were too hidebound to do so and have lost 10 years in the process.