5 ms·
Imagine a Windows based on Unix, like OSX, instead of being a derivative of VMS. It could so easily have happened.
by simonh 10y ago
Imagine a Windows based on Unix, like OSX, instead of being a derivative of VMS. It could so easily have happened.
- ryao 10y agoIt could still happen given the work Microsoft Research did on Drawbridge. It is public knowledge that they use it on Azure and with Drawbridge, they could rebase on UNIX. I doubt that it would happen given that Microsoft's modus operandi is to make as much money as possible by trying to lock people into their products, with Windows being the primary product on which they want people to be dependent.
- simonh 10y agoWow, just looked up Drawbridge. It's a shame MS Research stuff rarely goes anywhere. That looks like top-shelf engineering.
- contextfree 10y agoIn this case they shipped. The Windows Subsystem for Linux is based on the picoprocess design that originated with Drawbridge. https://blogs.msdn.microsoft.com/wsl/2016/05/23/pico-process-overview/ https://blogs.msdn.microsoft.com/wsl/2016/05/23/pico-process...
- pjmlp 10y agoThat is a misconception. Drawbridge powers the pico kernels infrastructure on Windows and is the basis of the new Ubuntu/Windows subsystem. The research in Singularity and Midori were used in MDIL compilers targeting .NET AOT native code generation on Windows 8.x and the follow up changes that lead to .NET Native. Also F# started as a MS Research project. The theorem provers used to validate Windows drivers were also a MS Research project. LINQ, .NET contracts and Fakes framework also started as MS Research projects. Some Haskell and OCaml researchers are on MS Research payroll. There are tons of other examples.
- nixos 10y ago> I doubt that it would happen given that Microsoft's modus operandi is to make as much money as possible by trying to lock people into their products, with Windows being the primary product on which they want people to be dependent. How easy is it to port the average program from MacOS to Linux? While the Kernel may be close enough, the window library is so vastly different that it's probably the same work to port from windows to Linux as to port from MacOS to Linux
- nitrogen 10y agoPossibly GNUStep can help with the older APIs.
- meddlepal 10y agoThis seems like the path forward as far as MS is concerned. Laying a *Nix user land on top of NT which they seem very happy with and in no rush to throw away.
- gvurrdon 10y agoThat would have been very interesting to see. I have often wondered what would have happened if they'd gone in that direction, perhaps including some sort of WINE-derived code to allow legacy applications to run.
- gvurrdon 10y agoI also wonder why such a comment is worthy of downvoting. Perhaps someone would care to enlighten me?
- bluedino 10y agoHad they worked out the MS-DOS compatibility, it could have. The other issue was performance. UNIX systems at the time needed a far faster CPU and graphics, and far more RAM and disk space. Faster = much more expensive. Which is also why Windows systems were 1/4 the price.
- gattilorenz 10y ago> Had they worked out the MS-DOS compatibility, it could have. Xenix collector here, I would say they had (sort-of) MS-DOS binary compatibility, as you could run some DOS programs on Xenix 386. I think it's only limited to real mode programs, but I tried it a couple of years ago and it worked. Not to mention that on Xenix you could develop for both platforms (well, more than that: with the right setup you could target DOS, Xenix 8086, Xenix 286 or Xenix 386), that's quite an advantage. On a side note, a good collection of Xenix manuals can be found at http://www.tenox.net/docs/ http://www.tenox.net/docs/.
- bitwize 10y agoXenix had a DOS compatibility layer called VP/ix. Sometimes, it even worked!
- cmrdporcupine 10y agoThe problem with Windows isn't its NT underpinnings. NT is a well-designed kernel designed by some really smart people. The problem was the absolutely awful userspace and Win32 they pasted over it. And then let that dig tendrils down into the lower levels of the kernel. I remember administrating systems running NT 3.51 and finding it actually not that bad apart from the usual Windows fault of having to use the GUI for almost everything.
- mixmastamyk 10y agoNT 351 was a rock, I used it on desktop for a year or so and it never crashed. Compared to daily crashes on consumer Windows it was a revelation.
- digi_owl 10y agoEven MS wants to get away from win32. Problem is that their continued support of it is what keeps corporations from looking elsewhere, as the business specific stuff is likely to be win32 based.