3 ms·
> Consider the three operating system families we are forced to choose from: Windows, Apple, Other (which I shall refer to as “Linux” despite it technically bei
by smacktoward 8y ago
> Consider the three operating system families we are forced to choose from: Windows, Apple, Other (which I shall refer to as “Linux” despite it technically being more specific). All of these are built around the same foundational concepts, those of Unix.
Wait, what?
Linux and macOS, OK, sure, they are based in varying degrees on Unix. But Windows? Windows has no appreciable Unix heritage. The DEC roots of the people Microsoft hired to develop Windows NT mean that modern Windows has some similarities to systems like VMS, but VMS isn't Unix and never was.
> Oh, wait a minute, this is still the only way we can get anything done in the world of programming! Typing textual orders into a “terminal” or “console” application—nothing more than an emulator for the teletype!!
On Windows? What?
> 3. “Everything is a file”
...
> 4. An obsession with unstructured text
The only thing I can figure here is that the author is familiar with Macs and Linux, where these assertions are all true, and is just assuming that they must therefore be true on Windows as well. Where they very much are not.
Windows has had some convenience features layered on top of it to make it more comfortable for people familiar with Unix to use, but deep down in its lizard brain it is very much not Unix and was built around a completely different set of assumptions. Windows doesn't assume everything is a file, interprocess communication in Windows has never been about piping text between processes, Windows has been GUI-first rather than terminal-first from Day Zero, et cetera et cetera et cetera. It's just a completely different thing than Unix and Unix-derived systems like Linux and macOS.
One can argue that this is a strategic weakness for Microsoft, as the world (especially among developers) has more or less settled on Unix as the One True Way to Write an Operating System, and thus the more different Windows is from Unix the harder it becomes for them to sell Windows to people. But listing all the legacy baggage that Unix-derived systems haul around with them and then saying "oh yeah, Windows has all that junk too" is just incorrect on a fundamental level. Windows carts around plenty of legacy baggage of its own, but none of it has much to do with teletypes or text pipes.
- JdeBP 8y agoThe author got a number of things wrong, but the thing that has surprised you is one of the few that xe actually got right. The handle-based API and subdirectories, introduced in MS-DOS version 2, were both Unix concepts added to MS-DOS that remained in DOS+Windows and in its successors OS/2 and Windows NT. (This wasn't the only Unix concept to cross to the IBM+Microsoft world. 32-bit OS/2 even changed to keeping system time the same way that Unix did, with a 64-bit count of seconds since the Epoch.) Command pipelines were right there in MS-DOS 2, as well. Peter Norton wrote a chapter about them in his MS-DOS and PC-DOS Users Guide in 1984. Ironically, the thing that you have got wrong, in your turn, is your assertion that "an obsession with unstructured text" is actually true of MacOS and Linux in the first place. Most textual data files in such operating systems are in fact structured into records and fields; many data files (especially on the BSDs with termcap, the account database, and various others being Berkeley DB files) are not text at all; and there has been one particular database (the login database) that has not been text since 1BSD and Research Unix version 7.