https://mspoweruser.com/wp-content/uploads/2020/04/windows-c...
https://mspoweruser.com/wp-content/uploads/2020/04/windows-c...
An alternative explanation is that this intentional imperfection exists to match the unavoidable imperfection which occurred when the cursor graphic was originally drawn as tiny low resolution 1-bit pixel art. It looks correct because we're used to it being slightly wrong. And when viewed at a normal size, the difference is barely perceptible anyway.
[0] https://mspoweruser.com/why-windows-10s-asymmetrical-cursor-...
[1] https://old.reddit.com/r/TIHI/comments/fwnep0/thanks_i_hate_...
[2] edited, thanks jusuhi
Oh, but it was. Here's Apple HIG from 1987 listing extensive bibliography on the subject: https://x.com/andy_matuschak/status/1447409175596699652 (here's the full PDF: https://andymatuschak.org/files/papers/Apple%20Human%20Inter...)
Modern "designers" apply as much thought and care as a hungry goldfish at feeding time
> there's a (pre-release) 1985 HIG that's quite different. It includes e.g. case studies (useful!), and an extended discussion of Jung's theories of intuition and how they should influence your designs (!!)
The most modern "designers" read is the labels on grocery store items.
> wasn't always done with as much thought
While Apple cared a lot about perfecting UX, Microsoft had other priorities.
I don't have a link to OS-level considerations, but here's a series of articles on how MS Office's original ribbon came to be: https://web.archive.org/web/20080316101025/http://blogs.msdn...
Making things pretty wasn't a priority for Microsoft the same way it was for Apple. But I wouldn't call that UX.
Looking back from an era in which Apple's sensibility has prevailed, it's quite hard to explain the extent to which Microsoft, at least until the late '90s, really didn't care whether their software looked good. They genuinely didn't see it as important.
Additionally, Windows 10/11 go to some extent to hide cursor scaling from applications. Win32 GDI/USER calls only see the base 32x32 arrow cursor and only DXGI Output Duplication (screen capture API) can see the real cursor. This causes other problems, though, such as various bugs and inconsistencies with custom cursor images.