diff --git a/README.md b/README.md index 4be650f..ad6ea1c 100644 --- a/README.md +++ b/README.md @@ -35,8 +35,9 @@ Some quirks I've noticed since I started working on this: - In Linux, when a parent process dies (such as, a process spawns a child process and then ends itself), the kernel politely adopts the child process to avoid it from floating as an orphan. Windows, on the other hand, is a merciless sadistic psychopath and will leave processes connected to a ghost PID. Sometimes, Windows frees the parent PID up and something immediately snatches it, so a parent PID can be deceiving. - The kernel stuff is complicated as heck for no reason. Like everything is so separated and needs very weirdly specific workarounds that it's almost eerie. - To get the uptime of a process, the Windows kernel politely tells you the raw FILETIME of a process. But that isn't exactly... readable. In fact, it represents the amount of 100-nanosecond intervals since January 1, 1601, in the UTC timezone. Microsoft, WHAT? Literally every other piece of software uses Unix time, which is the number of **seconds** since January 1, 1970, in the UTC timezone. In Linux, you can just read the /proc/PID/stat file and get the uptime in seconds. -- Everything in Windows that's stupid like this is simply because of legacy reasons. While newer versions of Windows look like a shiny new (although heavily bloated) OS with a nice user-friendly UI and a whole crap ton of WebView2's and RAM hogs, the kernel is still the same mess of code that was written like 30 years ago. To cut them some slack, the Windows NT kernel was worked on by a bunch of people simultaneously which can lead to conflicting ideas, decisions, and other stuff. Linux, on the other hand, was written by one person (Linus Torvalds) and a small team of volunteers, so it has a much more consistent design than whatever this monstrosity is. Anyways, the other reason is compatibility. Even if Microsoft _wants_ to change something, millions of facilities use custom-written applications that rely on old behavior, especially things like hospitals and other infrastructure. (I bet banks are still written in COBOL or FORTRAN tho lol) - +- Everything in Windows that's stupid like this is simply because of legacy reasons. While newer versions of Windows look like a shiny new (although heavily bloated) OS with a nice user-friendly UI and a whole crap ton of WebView2's and RAM hogs, the kernel is still the same mess of code that was written like 30 years ago. To cut them some slack, the Windows NT kernel was worked on by a bunch of people simultaneously which can lead to conflicting ideas, decisions, and other stuff. Linux, on the other hand, was written by one person (Linus Torvalds) and a small team of volunteers when it began, and every addition is still carefuly scrutinized by Torvalds himself, so it has a much more consistent design than whatever this monstrosity is. Anyways, the other reason is compatibility. Even if Microsoft _wants_ to change something, millions of facilities use custom-written applications that rely on old behavior, especially things like hospitals and other infrastructure. (I bet banks are still written in COBOL or FORTRAN tho lol) +- Every new version of Windows is just a coat of paint over the other. Yes, this is common knowledge, and related to the previous statement, but it's still something worthy of pointing out just because how bad it was done. It's like the landlord treatment. Every shiny new Windows version adds new features on top of the previous version. While a large variety of the features are good (except Microsoft Copilot, which is never useful and will probably never be; not to be confused with GitHub Copilot, which is somewhat competent), most of these add an extra layer of complexity since they have to be deeply connected to 30 years of Microslop's mistakes, which they cannot escape from as it haunts them in every compatibility issue that comes up. +- Okay, I've been roasting Microsoft up and down all day. While their initial start with the NT kernel code isn't exactly great, let's not forget Windows is still a software engineering marvel due to its seamless compatibility with virtually any piece of hardware. It is the main reason why it is so widely used. And for that reason, it is with utmost regret that we shall mourn for the fact Microsoft themselves has forgotten on what Windows really is, and decided to violently pump a bunch of LLMs down Windows' supratrochlear vein and slopify it into a nightmare-haunting pile of toxic, boiling, aneurysm-inducing, dignity-erasing garbage people are forced to use. ## How to build