4 ms·
Nah, it's Apple's fault. Not regression testing against major apps is pure incompetence. Also, this in the comment: > [a user] Please try any way of getting
by x0x0 1y ago
Nah, it's Apple's fault. Not regression testing against major apps is pure incompetence.
Also, this in the comment:
> [a user] Please try any way of getting in touch with Apple engineers you can. As a project, we don't have a better connection to Apple than you do.
>
> One approach might be the engineer who replied to the Bluesky post that someone linked to above about the input issue.
Pure incompetence. Major projects have no way to do anything but ping randoms on socials.
- bombcar 1y agoThis is downvoted, but it's true. It doesn't matter who's fault it is in some Aristotelean sense, what matters is the user upgraded to YOUR new OS, and now shit don't work. Raymond Chen and Microsoft got this, years ago. Joel talked about it. You make shit work, even if it's the software being a fuck.
- kridsdale3 1y agoNo time to do that when you need to re-do the entire UI of 100 apps for no good reason other than to make an iMac indistinguishable from an iPad.
- sgerenser 1y agoOr, as some OS maintainer once said: WE DO NOT BREAK USERSPACE! Seriously. How hard is this rule to understand? We particularly don't break user space with TOTAL CRAP.
- aw1621107 1y agoThis situation seems to be more analogous to an out-of-tree driver which reaches into kernel internals, which Linux does break all the time.
- mrheosuper 1y agoif the out-of-tree driver does not touch kernel space, it should not be broken.
- aw1621107 1y agoWell yes, if the out-of-tree driver sticks to public stable APIs it shouldn't be broken. And analogously here, if the software in question stuck to public stable APIs and didn't reach into private internals it shouldn't have broken.