Why Windows sucks (the tip of the iceberg)
- The whole system seems to be based on some fundamentally bad and annoying design principles.
- Everything is giant, rigid, monolithic block.
- There is no simple way to combine two things.
- In Unix you solve problems by combining existing programs.
In Windows you just add another monolithic block.
- Shitty GUIs all over the place. Seriously.
- As a result, it's hard to automate things.
- Naming sucks. Always. C:\Users and Settings, seriously? (Yes, it has been fixed)
As a hilarious example: syswow64 contains x86 DLLs, system32 contains amd64 DLLs.
- Special cases abound.
Compare Unix daemons to Windows services.
Compare Unix X11 programs to Windows magic graphical programs.
Compare Unix text config files to the Windows registry.
- The system as a whole is insanely complicated and impossible to understand.
- The whole system is impossible to debug. For many problems the only solution is "reinstall".
- Swapping out the kernel. Why.jpg
- Documentation sucks, it's often ambiguous and sometimes outright wrong. Since there is no source, you're basically fucked in that case.
- The API sucks completely.
- Function names like FindClosePrinterChangeNotification
- Functions which try to do 20 things at once
- But also unnecesssarily specialized functions and many functions which do mostly the same (WaitForSingleObject, WaitForMultipleObjects, WaitForMultipleObjectsEx, WSAWaitForMultipleObjects etc etc etc)
- At least 10 parameters on every function, seriously every function call has at least one NULL parameters
Unix open() has two parameters, Windows CreateFile() has seven
- An inconsistent naming convention
- Too many (i.e. more than one) calling conventions
- Bad C practices are mandatory, like casting between different pointer types.
- The driver system sucks.
- You get some binary blob from a hardware vendor (we all know how good they are at writing software).
- Windows by itself has almost no drivers.
- This discourages hardware vendors from making good and/or compatible interfaces.
- Thus, installing a windows system is a pain in the ass and the system as a whole is made more unstable than necessary.
- Charset handling is terrible. Completely terrible. Lobotomized-monkey-on-crack terrible.
- While the system pretends to be based on Unicode, special code pages are still common.
- Two versions of every text handling function (i.e. any function with a string argument). Seriously?
- But you still have to manually convert before writing to a file.
- Unicode-capable code has to use "wide" versions of everything.
- Windows uses UTF-16 in wchar_t* in its "wide" interface (This is not a joke).
- Spaces in file names are common in standard file names, but much code does not support it. What the hell.
- Lots of bullshit which unnecessarily deviates from existing de-facto standards all over the place:
- Drive letters.
- \ as a path name separator. What the fuck.
- CRLF line terminator
- The shell sucks. Totally. (PowerShell is even worse)
- No sed, no awk, no fun.
- The terminal is complete shit.
- Every message, signal or output from any tool, program, utility or solution is unnecessarily wordy, loquacious or verbose, i.e. in simpler terms it uses many more words than are absolutely necessary to describe something plain, simple and straightforward, while often giving not enough information or data to understand, analyze or debug a potential unusualty or problem.
Consult your system administrator for further information.
- Terrible localization (frankly no localization is often the best localization). MS-Dos-Eingabeaufforderung, anyone?
- Stuff like NETBIOS or "My Network Places" which never works.
- The GUI follows best practices like randomly popping up modal dialog boxes and focus stealing.