Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

You can't unit test for taste

dev.karltryggvason.com

Post reply on HN
Print view View original

151–157 of 157 posts

Re: You can't unit test for taste

#151

Post by sscaryterry »

usef- wrote: post #149
vkou wrote: post #147

Earlier quoted context omitted.

By the time the context menu was ubiquitous, their mice still did not have two buttons. Just because the feature is available somewhere else in the UI doesn't mean that the shortcut for it must be a two-handed one.

I've been able to plug in any two buttoned mouse for the 22 years since I first used a Mac. Their own trackpads and mice allow two finger tap to be enabled for advanced users (but on a laptop one finger can press ctrl while the other taps). I don't know how far back you're talking about when you imply no support for them. But I remember noticing years ago a large room of tech professionals and 100% of the Windows use…

This is only because IMHO, the trackpad is something you can "live with" (edit: on a Mac) temporarily. It beats carrying a mouse around. Having said that, I know a UX designer that only uses the trackpad. Boggles my mind.

Re: You can't unit test for taste

#152

Post by vkou »

usef- wrote: post #149
vkou wrote: post #147

Earlier quoted context omitted.

By the time the context menu was ubiquitous, their mice still did not have two buttons. Just because the feature is available somewhere else in the UI doesn't mean that the shortcut for it must be a two-handed one.

I've been able to plug in any two buttoned mouse for the 22 years since I first used a Mac. Their own trackpads and mice allow two finger tap to be enabled for advanced users (but on a laptop one finger can press ctrl while the other taps). I don't know how far back you're talking about when you imply no support for them. But I remember noticing years ago a large room of tech professionals and 100% of the Windows use…

> I don't know how far back you're talking about when you imply no support for them.

It's not 'no support', it was an insane default. For all the talk of 'easy to use', there's a reason context menus exist. You can't just cram every context-specific interaction into an omnibar or a leftclick. Non-trivial software is complicated. Adding that friction to its use does nobody any favours.

Yes, in the decades since... Trackpads have gotten a lot better, but at the time Jobs was pushing for that nonsense, they simply weren't good enough. (And didn't exist at all for non-laptop computers.)

Re: You can't unit test for taste

#153

Post by usef- »

sscaryterry wrote: post #151
usef- wrote: post #149

Earlier quoted context omitted.

I've been able to plug in any two buttoned mouse for the 22 years since I first used a Mac. Their own trackpads and mice allow two finger tap to be enabled for advanced users (but on a laptop one finger can press ctrl while the other taps). I don't know how far back you're talking about when you imply no support for them. But I remember noticing years ago a large room of tech professionals and 100% of the Windows use…

This is only because IMHO, the trackpad is something you can "live with" (edit: on a Mac) temporarily. It beats carrying a mouse around. Having said that, I know a UX designer that only uses the trackpad. Boggles my mind.

It's not temporary: Mac trackpads are precise and the multitouch gestures are integrated well with the system. Mice don't support them.

Re: You can't unit test for taste

#154

Post by usef- »

vkou wrote: post #152
usef- wrote: post #149

Earlier quoted context omitted.

I've been able to plug in any two buttoned mouse for the 22 years since I first used a Mac. Their own trackpads and mice allow two finger tap to be enabled for advanced users (but on a laptop one finger can press ctrl while the other taps). I don't know how far back you're talking about when you imply no support for them. But I remember noticing years ago a large room of tech professionals and 100% of the Windows use…

> I don't know how far back you're talking about when you imply no support for them. It's not 'no support', it was an insane default . For all the talk of 'easy to use', there's a reason context menus exist. You can't just cram every context-specific interaction into an omnibar or a leftclick. Non-trivial software is complicated. Adding that friction to its use does nobody any favours. Yes, in the decades since... Tr…

Defaults are for the normal consumer, non trivial software is not, I think? What's something you think must only exist in a context menu?

Note that in non-trivial or professional software it's typical to have a hand on the keyboard, because not even a second mouse button is enough. Hold 'q' while dragging to adjust exposure in capture one, etc. Or they have dedicated input hardware like mixing consoles. Or they plug in a speciality mouse.

Re: You can't unit test for taste

#155

Post by vkou »

usef- wrote: post #154
vkou wrote: post #152

Earlier quoted context omitted.

> I don't know how far back you're talking about when you imply no support for them. It's not 'no support', it was an insane default . For all the talk of 'easy to use', there's a reason context menus exist. You can't just cram every context-specific interaction into an omnibar or a leftclick. Non-trivial software is complicated. Adding that friction to its use does nobody any favours. Yes, in the decades since... Tr…

Defaults are for the normal consumer, non trivial software is not, I think? What's something you think must only exist in a context menu? Note that in non-trivial or professional software it's typical to have a hand on the keyboard, because not even a second mouse button is enough. Hold 'q' while dragging to adjust exposure in capture one, etc. Or they have dedicated input hardware like mixing consoles. Or they plug…

All software is non-trivial. You weren't buying a $3000 computer in 1999 to only use 'trivial' software.

Re: You can't unit test for taste

#156

Post by usef- »

vkou wrote: post #155
usef- wrote: post #154

Earlier quoted context omitted.

Defaults are for the normal consumer, non trivial software is not, I think? What's something you think must only exist in a context menu? Note that in non-trivial or professional software it's typical to have a hand on the keyboard, because not even a second mouse button is enough. Hold 'q' while dragging to adjust exposure in capture one, etc. Or they have dedicated input hardware like mixing consoles. Or they plug…

All software is non-trivial. You weren't buying a $3000 computer in 1999 to only use 'trivial' software.

Ok. So what's an example of something that should only exist in a right click context menu, for the average consumer?
Post reply on HN