https://blogsystem5.substack.com/p/windows-nt-vs-unix-design
From what I've read, Windows NT does have a good design underneath while Unix is simpler, but I don't think any windows version has offered the capabilities in a straightforward manner and easy to administrate. Too much awful layers as the parent comment says. While Unix has been mostly the kernel => the service manager => your service surrounded by a few concepts like users, unix sockets, file permissions,...
These technologies are battle-tested, and were adopted or replicated in Linux-land . Fore example, systemd does event logging and service management. Likewise, Linux file permissions haven't really stood the test of time, enterprise-grade systems use ACLs, which again, are a retrofit into Unix/Linux, but native to windows. For Linux, you have a choice of these implementations, but most are built on top of the OS, and each have their fanbases.
The 'traditional way' of sysadmin-style semi-custom Linux boxes, each with their own permissions setups and init scripts have thankfully gone out of vogue.
The creators of UNIX inherited the hierarchical file system of Multics, but they have abandoned ACLs, considering that they are too complicated for small mini-computers with a few users, and they have replaced the ACLs with the well known UNIX file permissions.
So ACLs are not some Windows or Microsoft innovation. Both the POSIX ACLs and the Windows NT ACLs have resurrected the Multics ACLs.
Regarding system logs and service scheduling, Windows has made only negligible improvements over UNIX.
Neither are really recognizable from their "roots" these days. The only certainty is that updating Windows still takes bloody ages.
Today I took an Ubuntu VM from 24.04 to 26.04 - it took about 10 minutes (that includes downloading the updates). It was a fairly simple system and I didn't have to repair anything. The service was actually up for most of the update.
I've run Exchange updates that have lasted most of an evening and night and that was on a single box Exchange on prem deployment.
On Gentoo Linux an emerge -Uva --deep --newuse @world can take a little longer than a Windows update sess but you are compiling the OS from source 8)
DEC even sued Microsoft and Microsoft settled (sound familiar? DOS? Can't Microsoft invent anything of their own?).
Hey, they got it quite reliable eventually (Windows 2000 timeframe), but still.. To say Linux is 1970s tech and WinNT ISN'T seems a real stretch.
And if other more modern kernels offer significant improvements over them, I wonder why we are not seeing them. Should be easy enough to add a Linux or Windows syscall layer to a modern kernel like that.
In the beginning, the NT kernel API was a mixture a functions taken from VMS (mostly for asynchronous I/O and thread/process management) with functions taken from UNIX (mostly for classic I/O), where most functions had various corrections or enhancements in their lists of parameters in comparison with their models from VMS and UNIX.
The later Windows NT versions added some innovations, e.g. I/O completion ports in Windows NT 3.5, waitable timers in Windows 4.0, and so on, but there were not many such innovations and most were not very important.
Around 2000, one could claim that Windows NT is a much more modern OS than Linux.
However, after 2000 Linux started to add a lot of innovations over what is specified by POSIX. Today, any high-performance application running on Linux that uses the POSIX API instead of using Linux-specific features, makes a big mistake.
Nowadays, for many applications Linux has a better API than Windows, but the Microsoft developers are not stupid, so in recent years they began to incorporate into the Windows kernel some of the more important Linux kernel innovations, like futexes and io_uring.
Unfortunately, as I understand it, it basically needed to pretend to be Win 9x on release due to Microsoft's (understandable and smart) focus on backwards compatibility, so there's effectively a layer on top of NT that hides its most powerful capabilities. Then there's all the cruft Windows layers on top of the kernel, so one could be forgiven for missing the gem sitting beneath the mound of manure.