The author is not wrong, but swimming in the shallows. It's a very old problem that goes back more decades than are accounted for here. To their credit, at lea

The author is not wrong, but swimming in the shallows. It's a very old problem that goes back more decades than are accounted for here. To their credit, at least when the joint venture between IBM and Microsoft happened around OS/2, CUA still set a broad standard that was widely met and meant that many of these problems were rare, or at least the keyboard was guaranteed to work consistently. Apple does not deserve the free pass it gets here. Why? Because design choices are not governed by designers. Rather, they are governed by cost and time-to-market, much like car interiors, and chosen from a shared parts bin. Depending on the ISV this means that the GUI or widget toolkit may be Microsoft.net, Java, Qt, or 30 years of other toolkits recombined poorly ad nauseam. Frequently, this means the evil of two lessers since there are no clear winners. Users will continue to suffer as a result. I try to solve this with Sway on Linux, but the further into left field I go, the screaming just gets louder, not quieter.