I believe it is new. I’ve never seen them:
- put a upgrade os version under “updates”
- then select the upgrade os version instead the current version when there are multiple updates ( os patch, safari or xcode)
This comes from that short period where the Internet was meant to be the bonding agent for our global village bright happy future.
And it was always portrayed as a solution for arranging meetings for you and your friends or business people on the other side of planet.
I think the other idea from these times was abolishing phone numbers and using unified global email-like identifiers.
And in a way we got this on social media - some people use same account names everywhere - not mention keybase, and we also have instant messengers on smartphones in our pockets.
"And because Sega is working with Swatch, we wanted to encourage the use of the BEAT system."
This was also marketing driven, it seems.
Kinda telling, that they had timezone troubles, even when using Beat :)
"The BEAT system that shows up on the game screen isn't just based on the Dreamcast settings -- it's sent over from the server. And because there are so many different servers in different time zones, it was a bit of a pain to get all of that unified."
Hover the timestamp here on HN and you'll see it at least once in your life time :) I'm guessing it's mostly developers, especially ones working internationally, who come across it every day. Others seem to prefer to convert between people's timezone, while we just send UTC+00:00 to each other.
I was about to comment that it's not UTC, it's in my local time. Then I remembered my local time (Europe/London) is currently equivalent to UTC, so I have no idea what it's actually displaying (it's not indicated in any way).
It's actually a problem in these parts that it's not obvious to us whether a time is in UTC or local time. I've found so many things displayed in UTC that people have assumed is local time then summer comes around and everything is off by an hour.
I agree with the article. What the author doesn't answer is why we're seeing so many visually noisy tables. He seems to imply that designers don't know any better.
There are two different "modes" of looking at a table. One is just "superficially glancing" (like you look at a picture), the other is more like reading, because you look for some specific piece of information. When glancing at a table, the one with more colors and icons looks more pleasing, while plain text looks boring. But when reading the table to get information out of it, the "boring" one (if it's well done) is probably more efficient and a better experience.
And here is the problem: when presenting designs to stakeholders, 100% of stakeholders just glance at the table and always prefer the more colorful table with many icons — they don't realize that actual users, who need to get information from the table, would be better off with the "boring" table.
https://www.youtube.com/watch?v=VjpcLplkMUs&t=2s
reply