> but what's hard for me to process is why it’s 5 or 6 years later and it’s still not fully fixed

Because Apple's (the company's, as a whole) bug -> triage -> engineering -> deployment process is fundamentally broken, and obviously has been for decades at this point.

Say what you want about MS, but at least critical issues that actual customers are experiencing tend to get fixed.

Apple seems to have some weird 'maybe someone will look at it, if they have time, after they get done implementing new features for the next release' process. (Glaring example: daisy chaining DisplayPort support)