> As opposed to object-oriented interfaces like for example Windows NT, which allows for elegant shells like PowerShell.
Now let the downvotes flow in…
No downvote from me!
I always found UNIX's everything-is-a-bag-of-bytes to be a huge pain, and file descriptors even worse.
This is a hard pill to swallow for many *nix die-hards, but I would say that objectively speaking, Windows NT has a better core OS model than Unix-like OSs, including the driver model, the filesystem API, the process management API[1], and the overall plug-and-play-ness of NT.
[1]: The OP article mentions this paper by Microsoft Research, but claims it doesn't offer alternatives—it does. It explicitly mentions posix_spawn and CreateProcess. https://dx.doi.org/10.1145/3317550.3321435
I've found delving into the structure of Windows NT (and Windows in general) is an endless stream of fascination after another. Almost 30 years of being a Windows wizard and I'm still like a kid in a toy store any time I go through it.
On the surface it seems like madness, but taking a proper look quickly shows there were and are very smart and wise people behind Windows's core.
Now let the downvotes flow in…
No downvote from me!
I always found UNIX's everything-is-a-bag-of-bytes to be a huge pain, and file descriptors even worse.
This is a hard pill to swallow for many *nix die-hards, but I would say that objectively speaking, Windows NT has a better core OS model than Unix-like OSs, including the driver model, the filesystem API, the process management API[1], and the overall plug-and-play-ness of NT.
[1]: The OP article mentions this paper by Microsoft Research, but claims it doesn't offer alternatives—it does. It explicitly mentions posix_spawn and CreateProcess. https://dx.doi.org/10.1145/3317550.3321435