3 ms·

I wasn’t discussing mouse acceleration, but it’s just the same. The acceleration curve hasn't changed since 1984, to the best of my knowledge. I don’t see Mac u

I wasn’t discussing mouse acceleration, but it’s just the same. The acceleration curve hasn't changed since 1984, to the best of my knowledge. I don’t see Mac users complaining. Should Apple expend effort to accommodate ex-Windows users? It’s not my call, but I don’t think they should. Regarding the pressing demands, how about a notification system that’s not a compete UX joke or a reliable and simple file sharing solution that doesn’t require the user to be aware of the SMB or SSH protocols? I could spend the whole day listing lower hanging fruits than meeting the particularities of ex-Windows users. The number of system developers with deep knowledge of macOS, Swift/ObjC and willing to live in Cupertino is surprisingly small. It’s a very limited resource and it shows, given the number of years some glaring bugs survive with macOS every release.

eviks 3y ago
You see Mac users complaining, they are right here in this thread, you just choose to dismiss the complaints. Just like you again ignored that Apple also disagrees with you since they fixed this bug And you haven't explained the most important thing- the blocking part, "resources are limited" gives you nothing of substance at this level, you actually need to know the amount of effort involved. How much time is needed to expose a different mouse curve? Would a better notification system be developed within that time?
- tambourine_man 3y ago
  Ask those Mac users if they're using the platform because their job requires them. You may be surprised. I haven't ignored that Apple disagrees with me, that's a fact, since they shipped the toggle. I'm arguing how they should spend their developer's time. >Would a better notification system be developed within that time? How about basic functionality, like being able to close a notification without some serious mouse gymnastic? That bug is 3 years old. Or having your music player display how much of the song has been played without requiring a hover, like any sensible music player has done since forever, iTunes included. Or a System Preferences/Settings that's not a flabbergasting disaster. Priorities.

eviks 3y ago

You see Mac users complaining, they are right here in this thread, you just choose to dismiss the complaints. Just like you again ignored that Apple also disagrees with you since they fixed this bug And you haven't explained the most important thing- the blocking part, "resources are limited" gives you nothing of substance at this level, you actually need to know the amount of effort involved. How much time is needed to expose a different mouse curve? Would a better notification system be developed within that time?

tambourine_man 3y ago
Ask those Mac users if they're using the platform because their job requires them. You may be surprised. I haven't ignored that Apple disagrees with me, that's a fact, since they shipped the toggle. I'm arguing how they should spend their developer's time. >Would a better notification system be developed within that time? How about basic functionality, like being able to close a notification without some serious mouse gymnastic? That bug is 3 years old. Or having your music player display how much of the song has been played without requiring a hover, like any sensible music player has done since forever, iTunes included. Or a System Preferences/Settings that's not a flabbergasting disaster. Priorities.