zlacker

I love how those stories of the early years are so different from what I think of looking at companies today -

> Jeff picked me up at the airport, and we drove to Microsoft's main building where we were joined by Neil Konzen, a talented 23 year old who was Microsoft's main systems programmer on the Macintosh. I knew Neil from his days as an early Apple II hobbyist, when we collaborated on adding features to an assembly language development system when he was only 16.

Just... "Microsoft's main systems programmer on the Macintosh" is such a weird sentence to read today. On the other hand, Microsoft also shipped Xenix, a full-on licensed Unix™ OS before they shipped DOS.

>>yjftsj+(OP)
Microsoft is still the largest Mac software vendor, and they are again in the Unix distribution business with WSL. The more things change, I guess...?

>>yjftsj+(OP)
You do realize that Microsoft Word has been on the Mac since 1985 suite and even the first Microsoft Flight Simulator was on the Apple II?

Also Applesoft basic was derived from Microsoft basic?

Yes, they did copy the operating system but that doesn't mean that the Mac Platform is unimportant to them.

>>yjftsj+(OP)
The really direct and aggressive negotiating from Jobs and Gates also makes for an interring read.

>>zitter+F
I'm perfectly familiar with Microsoft being an application vendor for Apple's platforms, long before that was Macintosh:) What threw me off with the notion of them employing a systems programmer for a non-MS OS.

>>yjftsj+(OP)
Windows NT is designed out of the box for extending and embracing Unix. The whole Linux Subsystem thing isn't something new that required deep reworking of the kernel.

>>zitter+F
> the first Microsoft Flight Simulator was on the Apple II?

Back then, Flight Simulator was still owned by subLOGIC. Microsoft got a license from them to make the IBM PC version.

>>sansno+B5
On the other hand, WSL2 is based on virtualisation rather than NT kernel personalities. Apparently building it 'on top' or 'inside' NT ends not not being good enough.

>>yjftsj+A2
It makes more sense when you consider that 'systems programmer' doesn't mean 'writes operating systems' (especially back then) and the line between application and systems programming was quite blurry (double especially back then).

>>zitter+F
Microsoft buying a big chunk of Apple (admittedly to stave off antitrust claims that there was no competition in the OS market) is a major reason Apple is alive today.

>>yjftsj+(OP)
Neil Konzen's P.L.E. (Program Line Editor) helped make my early days of Apple II programming bearable. It later was expanded into GPLE and published by Beagle Bros.

>>onepla+1c
I don't think that's a failure of the NT subsystem approach, I think that's just that Linux turned out to have a massive and changing ABI surface and Microsoft didn't want to try and recreate the whole thing by clean room reimplementation. Yes, there were some difficulties because of different underlying primitives, but in my outsider's opinion, they could have made it work if they've been wanting to spend the time and effort.

>>sansno+B5
The Linux Subsystem actually doesn't use the NT subsystem technology that you're thinking of. They did end up inventing a few new kernel concepts (like pico processes) in order to do WSL v1.

>>pavlov+A
> they are again in the Unix distribution business with WSL.

For anyone who doesn't get this reference:

https://en.wikipedia.org/wiki/Xenix

https://en.wikipedia.org/wiki/Windows_Services_for_UNIX

>>yjftsj+Og
The problem they couldn't solve is file system performance -- there's just too much of difference conceptually between files in Windows and files in Linux to make it perform reasonably well for the sorts of jobs people were using.

In the end, it just makes more sense to pull in the actual Linux kernel than to try and achieve the same performance semantics.

>>wvenab+fh
Indeed. There was a windows services for Unix subsystem based on Xenix mentioned elsewhere and that was based on the subsystem architecture.

When you use it, you get a nice Korn shell and it is built on PE binaries linked against PSDLL.DLL. there's a functioning but very old version of GCC that ships with it.

The PE binaries mark up the desired subsystem to be invoked so you don't have to be in the environment to execute one - the kernel takes over.

PSDLL acts as a translation layer for NT much as kernel32 does for win32. You can't run unmodified Linux binaries like you can with wsl. On the other hand, WSL requires that you invoke lxss with some special com magic to get access to Linux first so you can't just exec an elf file directly. The Pico processes you mentioned - these allow the kernel to install specific handlers/translators of their syscall functionality into the windows kernel.

So yeah architecturally they're pretty different and WSL isn't really the same subsystem concept they started with. On the other hand it that's probably a good thing because everything needed a rebuild for SUA.

>>wvenab+ui
Windows file system performance in general is abysmally bad, we are talking Linux being 10x-100x faster on mass operations on small files for instance.

Due to this lots of Linux stuff is based around huge masses of tiny files (build processes, VCS, docker, etc) and there was just no chance the windows kernel was ever going to come remotely close performance wise.

>>zahllo+Ql
I'm convinced that SUA system only exists so Windows can claim "POSIX compliance" as required for various government contracts.

>>sansno+B5
You should read the book Showstopper! to learn that NT was actually designed to be as far away from Unix as it could be. Dave Cutler, NT’s chief architect, hated Unix with a passion. He thought it was a rubbish OS. The internals are based on VMS, Cutler’s previous OS. That’s why NT has never been a good posix system and why microsoft has essentially given up with WSL2 and is now just running linux in a vm.

>>alasda+Hc
On the other hand, Apple unintentionally granting a perpetual license on their interpretation of the WIMP GUI (admittedly not without perusing the look-and-feel lawsuit) is what kept Microsoft in the OS business.

>>Joeri+bv
Great book. Another interesting wrinkle that’s been somewhat lost to time is that (as the book documents) NT was developed simultaneously on x86 and a RISC architecture (MIPS I believe).