Breaking MacOS is easy, if the fork bomb doesn’t work just create a function which recursively writes files until the disk is full. Unless they fixed it in the past 5 years, at that point even when the OS is set to delete files directly, it will still fail to delete anything. I couldn’t even remove anything with sudo rm -f, that just triggered a ‘not enough space to remove file’ error message.
Found that out the hard way when a program borked itself and filled the entire drive with log files until there was not even a single byte left. Fortunately I had a very small file in the bin, clearing that still worked and those few bytes were enough to be able to perform file deletes again. Never bothered to find out why MacOS behaved that way as I was able to ditch that OS entirely not long after, but perhaps somebody else knows.
But is it really Window’s fault when a software vendor decides not to support a newer Windows version, or a manager thinks cutting costs by not renewing a support contract is a great idea? I’ve seen plenty of software fail to compile on Linux because of, for example, slightly newer (or older) glibc versions being present. It’s not as if using Linux means software will magically run on every version out there.