Anatomy of the thread suspension mechanism in Windows
ntopcode.wordpress.com
ntopcode.wordpress.com
This interest has lead me to have a much better understanding of how and when things go wrong on my personal desktop, and how to troubleshoot them. I wonder how much of the hate Windows gets from developers is simply people feeling confused and left out of the information bubble.
Raymond Chen of "Old New Thing" fame and all his friends[1]
The creator of process monitor occasionally writes nice blog posts about troubleshooting[2]
A lot of historical NT stuff is still valid, or at least mildly relevant today.
[0]https://www.amazon.com/Windows-Internals-Part-architecture-m...
[1]https://blogs.msdn.microsoft.com/oldnewthing/
[2]https://blogs.technet.microsoft.com/markrussinovich/2005/10/...
Compare to https://www.macintoshrepository.org/1645-codewarrior-4-gold-..., which manages to look fine in a similar number of pixels.
If your source code/editor/fonts produces screen contents so ugly that people with taste can't bear to look at it, the end-user experience isn't going to be awesome.
Edit: I see now it's decompiled code. But the original source was probably written by someone looking at that same font (FixedSys?). Assuming that function originated in Windows NT, they would have been editing on an earlier version of Windows.
[1] https://www.hex-rays.com/products/ida/
[2] https://developercommunity.visualstudio.com/storage/temp/442...
You're somehow even critical of the "individual pixels". The individual pixels are in your screen and if you can't bear to look at them, get a better monitor.
What you're doing here isn't demonstrating taste. Your criticism is shallow and uninformed. This is at best snobbery.
Disclosure: Microsoft employee and generally annoyed by superficial snobbishness.