In 2014 Microsoft cancelled the dedicated SDET (Software Development Engineer in Test) role, triggering significant layoffs.
Before Linux took over the server market in 2000, Windows server was the dominant player in mid-market (enterprise market has IBM mainframes too). But you would have be old enough to remember that decades ago.
I use it since day 1
How would you say it has degraded?
Typescript paused new feature development to port to a new implementation language. It's too early to see if it's going to be better or worse for TS devs, will probably need to wait a few years (at least after the easiest things to pick are gone) to see if it was worth it for anyone who isn't building vscode sized projects.
VSCode was great, until LLMs hit the scene. Now there's a new update every 2/3 days either shoving more LLM-ware to the point that the seams are breaking, or it's a security bugfix for something that should never have been added in the first place.
You'd see occasional crash screens, but given the sheer number of machines out in the wild, having only a few crash once in a blue moon speaks amply to the reliability of the thing.
"The FDIC OIG is alerting banks about an increase in a type of fraud known as “ATM Jackpotting.” ATM Jackpotting involves criminal actors accessing ATMs and placing malware software on the system, enabling them to illegally dispense cash from the bank’s cash supply. The process is often run by sophisticated and organized crime rings at both the physical location (accessing machine and hard drive) and operating in foreign jurisdictions (transmitting malware codes).
The FBI estimates 700 instances of ATM Jackpotting and losses totaling more than $20 million in 2025."
An ATM is actually simpler than a fruit machine. The latter has more reasons to refuse a payout!
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.
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.
Somehow it manages to be slower in uncontended cases so maybe in hindsight it wasn't that good. But on Linux you get permanently stuck threads if your NFS server is down.
Consider: exclusive file locking for almost everything. UNIX lets you delete or move an open file, the Windows kernel doesn't and this creates enormous complexity at higher levels of the userspace stack especially for any kind of auto updater. It's also one reason Windows updates are so painful.
Windows has pathetically low performance in the filesystem layer, largely thanks to its filter driver design. It's not uncommon to find apps written originally for Linux are basically un-portable to Windows because they assume fast file IO and Windows just can't provide it. This was also a major motivator of the WSL2 effort. Windows actually has a feature called Dev Drive. It's a whole alternative filesystem that's faster than NTFS. They call it Dev Drive because they assume only devs need good filesystem performance (gah). You can't run Windows itself on a Dev Drive though, because of tech debt-y "reasons".
This ridiculous approach of assuming developers are special is carried over to other things too. Windows supports symlinks but this support is nearly useless, because it's disabled out of the box for security reasons (symlinks play a role in some kinds of attack on Linux). So you have to turn on Developer Mode in the control panel to be able to use them.
Sometimes you'll see the Windows approach to security be praised (SIDs, object manager etc). It does have a more principled design than Linux, that's true, but the standard here is macOS/XNU not Linux and the Windows kernel's sandboxing support is far worse than macOS.
Windows processes are extraordinarily heavy compared to a Linux process. They take more RAM, start up much slower, and context switching is slower. Again, this difference often renders Linux software un-portable because they assume they can fork and exit processes very fast, but on Windows you just can't. You pretty much have to replace a multi-process design with threads.
Despite the Windows kernel not being a competitive advantage to Microsoft (IMHO), and despite that they run public symbol servers, they keep it closed source. If you really want to understand the Windows kernel you can do so down to the level of individual function calls with public information, but you can't actually read them. The reason is probably security-through-obscurity for DRM, Warbird and other such things, not that it seems to help much. This makes it frustrating to figure out what's going on.
Relatedly, the Windows kernel is an absolute war zone. It's nothing like Linux, which is a conventional textbook OS design. On Windows the kernel is riddled with deliberate traps, code obfuscation engines and "tilt sensors" designed to try and block attempts to hook internal functions by malware or other kinds of malicious software. This shows up in other places too: for example, the API to Linux is the system call instruction. On Windows the kernel theoretically doesn't have a stable syscall interface and you're supposed to go via public APIs like kernel32.dll, which in turn just forwards to ntdll. In practice it does have stable syscalls because MS never randomized the system call interface, so apps trying to detect hooking in userspace do invoke system calls directly (often for anti-cheat purposes). The result is there are like three different ways to invoke NT system calls, all of which are extremely overlapping and duplicative (kernel32, ntdll, system calls), all of which are used by apps in reality but only one of which is documented.
- File locking is a convention on Windows, not a necessity and you don't pay for it if you don't lock files (which is an unfortunate default btw).
- By filter drivers being slow, I think you mean antivirus and security stuff, which are an unfortunate reality of daily windows use, but aren't really caused by filter drivers being a thing. If you needed antivirus on Linux, I think you might incur a similar penalty
- I think symlinks would be nice, but I haven't ever really missed them on Windows. The things linux uses it for, like linking libraries are done differently on Windows
- Devs are special in some sense. You can't afford to break existing workflows on users machines. Just recently, the EU decided to replace Windows with Linux, discovered that stuff doesn't work, then promptly went back
- I appreciate that you call out Windows security as a positive, but as with many other subsystems, Windows has shipped with many systems that were production grade and built in, like security, ACLs, event logs, etc. etc. which are not part of Linux by default, and are the subject of endless debates as to how to implement them (some of them, like systemd, mirror Windows functionality)
- A concept of a Windows process doesn't really map to a Linux process. Linux processes are isolated threads, while Windows ones are containers (and don't even necessarily have a main thread). And afaik Windows processes aren't that heavy any more. Their heaviness came from loading gdi32 and user32 dll, as they expected to host GUI apps, on new Win versions, that's no longer necessary. But fork() style process management is foreign to Windows, and the one place where its useful in Linux, cli apps, Powershell has an entirely different design, where its more like a JITed scripting language, and ls or cp are not separate processes.
- I don't think heavily multiprocess designs are in vogue anyways (at least not how Linux does them), but in terms of RPC, COM multi-process RPC was much more efficient in Windows compared to things like eventfd. Android even added binder, which is a similar mechanism
Many of Windows' mechanisms are a bit long in the tooth, but arguing that Linux is better, then adopting a very similar mechanism in Linux years to decades later doesn't really show that engineering superiority.
I'm not a Linux hater btw, except in one thing - the fact that there's no good standard way to build and distribute binaries that can be expected to work on any reasonable Linux install is criminal.
IIRC it's more that the filter architecture itself is slow, but yeah Windows comes with some slow filters out of the box that don't help. There's a writeup somewhere about this from a Windows kernel engineer but it was years since I read it. AV is indeed the worst offender but Windows always has one, so <shrug>.
systemd is inspired by macOS Launch Services. I guess svchost is the closest equivalent in Windows, but it didn't play any role in the systemd design process.
Linux processes do contain threads, I didn't quite understand what you meant by saying they're not containers. There is now the concept of a Windows picoprocess but it can't do much and isn't used after WSL1 was removed, if I understand correctly. I agree that Windows doesn't really need cheap processes architecturally and native apps don't rely on them without that imposing much cost.
[D]COM isn't a kernel feature but the closest equivalent on Linux would be DBUS, not eventfd. I don't know how they compare in terms of efficiency, I'd expect about the same, although in a past life I actually worked on an open source implementation of DCOM!
I didn't argue Linux is better, I have plenty of beefs with how Linux works too :) The Windows kernel is rightly very popular because it offers a stable driver API, which in turn enabled a huge gaming and hardware ecosystem, for instance. But architecturally I don't see big differences between them tbh.
Now Midori, on the other hand... that really was different!
I see that in general Windows takes a "big monolith" approach to things that Linux can handle as a large array of small pieces. An app can be a few files on Windows, a help database is one file, a source code repository would be one file if all the VCSes weren't imports from Linux.
This might be Conway's law in action. On Windows you were more likely a proprietary shop writing software that just does what it should do - if you needed to change it then you changed the software. On Linux because it's a bazaar you have a lot more of trying to tinker with the things that are already there, or add on small pieces. The average unit of deployment on Microsoft platforms is (or was) Turbo Pascal or Visual C++ 6 or QuickBooks or Microsoft Office; the unit of deployment on open-source platforms is grep or sed.
But that's MY perception of that period of time. I intentionally avoided working for Windows-based places because it sucked so bad.
I agree. We're talking web servers here, not SMB file and print servers, which were mostly WindowsNT based and the contrasting vendor would be Novell until sometime in the late 90s.
The vendor of popular web server software over time is well documented thanks to 30 years of Netcraft. Unfortunately, we don't see the platform, but most uses of Apache were either Linux or Sun based, and Microsoft shops tended to use IIS and rarely anything open source. My own experience at the time was that things that ran on Sun was mostly java based, WebLogic.
https://www.netcraft.com/blog/march-2026-web-server-survey
According to the graphs:
Microsoft's share of the top 1 million busiest sites was never above 20% and has been steadily declining for the last 15 years. If you were serving a lot of traffic, you weren't (and aren't) using Windows to do it. And the majority of traffic has always been served by something other than Microsoft.
Microsoft reached over 50% in 2017 in marketshare of all sites, but traditionally has been limited to below 40% and has really dropped off since 2020. And (based on the graphs), that traffic probably migrated to nginx.
There was a period in here where Netcraft had to make a distinction between sites and servers. Cheapo web hosting services via virtual hosting was on the rise, and a massive number of domains/sites were all served from the same server, and it skewed the numbers in terms of vendor market penetration (think shared-hosting offerings like GoDaddy, the hosting industry was lousy with them). The back and forth churn was notable when some big hosting company switched their web server software and then hundreds of thousands of sites changed software vendors. I remember Microsoft making a big deal about this with marketing copy like "The most popular web server software on the Internet", which may have been true based on domains/sites, but not based on installed instances or most-served-traffic.
IME Microsoft was never a big vendor of web server software, unlike how they are a big vendor of desktop. People were aware of IIS as an option if you were a Microsoft shop, and I know some people who ran it (I once crashed my buddy's site using the perl WinNuke one-liner to put him in his place after bragging about his NT and IIS setup -- hi Noel!) but Sun dominated and where it didn't, it was open source solutions.
> I intentionally avoided working for Windows-based places because it sucked so bad.
Same.
The problem is making all the moving parts from all those people work together well. Weakest link is almost never the people but the complexity of everything.