Live data from Hacker News

Should toggle button show its current state or the state to which it'll change? (2010)

ux.stackexchange.com

301–303 of 303 posts

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#301

Earlier quoted context omitted.

The real pain is this WAS a solved problem in computers too. Almost all of the GUI OS's had a style guide. Usually 2-3 pages at most (usually smaller) and fairly easy to follow. Then everyone went bonkers and wanted to make their own. Then dump that all into one desktop and good luck... Every app is special.

I blame Microsoft for this. They release a completely new UI framework every 5 years, completely abandoning the old ones. The design is outdated and boring. The XAML based UI frameworks look terrible if you use the default settings, and force you to customize. It's great that it's easy to create custom UIs, but terrible for consistency between apps. On the Apple side, things look a lot better. They were able to keep…

Apple was just as bad. :( They switched at least 5 times in the early 2000s. Like you point out though they finally seemed to have calmed down.

MS had it in the bag too! Everyone wanted that 'sticker'. If you didnt have it almost no one would put your software on the shelf. To get that sticker you had to pass their usability tests that followed their style guide. Then they did like you said and switched it at least 2 times ever OS release.

Plus the web got in there and there were almost zero standards there. So we ended up with dozenes of framerworks that 'do it for you' and those have at least 3-5 generations of goop.

Re: Should toggle button show its current state or the state to which it'll change? (2010)

#303

Earlier quoted context omitted.

No, it doesn't?

Well, in this case, if one person says it does, and another doesn't see that it does, shouldn't the latter conclude they are likely missing something? If I say 'this truck hauls 2 tons up Mount Rainier' and evidently I do that, and you don't think so, wouldn't the rational conclusion be that the truck does it and you were unaware? I and many others, for centuries, have used etymology to understand meaning and history…

> in this case, if one person says it does, and another doesn't see that it does, shouldn't the latter conclude they are likely missing something?

In this case, we already have all the facts, so there's no reason to talk about what's likely.

Etymology is not informative as to meaning, and therefore cannot help anyone learn how a word is currently used. You are advocating for the Etymological Fallacy ( https://en.wikipedia.org/wiki/Etymological_fallacy ), but the name of the position you're taking should be a hint about whether it's actually a valid viewpoint.

Post reply on HN