Most US residents are going to be familiar with these time zones because you are more likely going to have to deal with multiple time zones in this set than any other international time zones. Television shows that announce to the broader country usually announce their times as, say, 11 Eastern/10 Central, because they'll be broadcast in both Eastern and Central time zones.
If I'm talking to someone in the US, I'm not going to bother prefixing the timezone with "US" because it's implied. But if I were talking to someone international, I'd be more likely to prefix "US", as in "this meeting is scheduled for 11:00 US Pacific time". This formulation has the added benefit of also describing whose daylight savings rule take effect in international settings.
..and to explain this one geographically, refers to the Rocky Mountains.
I’m not offended to learn about that stuff, I think it’s really interesting.
I agree that knowing the names of time zones shouldn’t be required, but I’ve only ever seen them displayed with their UTC offset beside them. When I get calendar invites for “AEST” I just look for that offset.
Just seems to me there are far worse things in the world to get worked up about /shrug.
As for your last point: that would apply to anything. There is _always_ something worse to get worked up about.
None. In fact, I personally thought this was an interesting little fact to learn. I didn't get worked up about it, all I said is that you shouldn't have to know it.
However, because Americans aren't very culturally sensitive with respect to foreigners, there's lots of little things that we do have to learn to access the so-called global internet.
Why is 12am before 1am? Makes no sense at all.
Just make it 06:00, 13:00, already :-(
I noticed a pattern that sometimes my alarm would refuse to ring in the morning but would ring at 8 at night.
I eventually noticed that it only happened when I stayed up late and reset the time/alarm at midnight and figured out that my clock was broken because it thought that 11 PM is followed by 12 AM.
It was more than a decade until I found out that it was correct.
Also, if you think timezones/calendars/seasons are bad, just understand that many people specifically have a difficult time with shifting their mind into a frame of reference where you can actually talk about time in the sense of "there is a moment in time $now, where I am, the clock displays X because formatting, the system clock is actually Y, and I want people in P to get experience Q which had relationship R to X and S to Y. I have libraries T, U, and V to work through the abstractive layers of. These same people are all inclined never to admit this difficulty or the complexity inherent thereto.
Throw in the fact most folks in the U.S. don't even understand the written script of more than a handful of places, and you have a recipe for !quality. Again though, there's only so much political capital you have as a Quality person, and prioritization tends to be the Project Manager's shtick.
Also throw in that the real optimization function in the market has been "the crappiest software that can still maintain usership" and it should be no surprise that the software packages that do localization right are far fewer in number than otherwise.
It's a rather sad state of affairs, but it is what it is.
Just... Wanted to point out there has been at least one person who brought up your points in design meetings everywhere they've been, and never ceases to end up receiving platitudes.