Earlier quoted context omitted.
I understand your point, but for an issue that's been addressed so many times, it doesn't sound necessary to get into details. The issue doesn't seem to be that Apple doesn't know but that they don't care. However, if I, as the author cared to justify that "it's not only me", I would have listed more posts and feedback. I feel like I have read at least 4 times about the broken keyboard, it should not be hard to find…
Well, presumably the page's intended audience is software developers at Apple. As a software developer myself, I am all too familiar with the unnecessary churn caused by vague bug reports. It saves time when people include details like error messages (when applicable), steps to replicate, expected result vs. actual result, etc. Besides, users and developers don't always use software the same way, have the same settin…
In the case of the iOS keyboard, I remember one bug that made the rounds (in the popular press!) after somebody recorded their typing in slow motion to validate it [0]. Once they documented it, everybody recognized the feeling and felt vindicated; but it took actual work to substantiate.
That’s the work it seems that Apple engineers should be doing. They have the telemetry, the source access, the design documents, the labs, and the time in their day to make a comprehensive study of it. Just as I can say “my car is handling funny around turns” and let it be the mechanic’s job to diagnose what’s wrong in mechanical terms.
There was a time when this humane aspect was Apple’s particular magic: engineering beyond technical requirements to the point of simplicity, ergonomics, “it just works”…
[0] https://www.macworld.com/article/2952872/heres-proof-that-th...