> Or better yet, just ditch timezones altogether.
that is quite a terrible idea IMHO (at least if done internationally)
sure they make international meetings/events harder, but for most people most of their live is bound to local time meanings even if you travel to another country. 7am is in the morning 7pm in the evening 11:59am is mid day etc. If you remove time zone then for some people 7am is morning for other it's mid day and for other noon. So creating a lot of issues for everyone just to make international remote meetings and events easier seems like a bad idea, not even considering the absurde level of practical issues a switch like that would cause for any country not around UTC+0. Even more so remote meetings and events normally involve software and and time zone confusions are very solvable there (display time dynamically in the time zone device currently displaying it (but with time zone suffix, and some considerations about storage wrt. changing time zones, also maybe add an option to display in home instead of current time zone)). Annoying is how few programs do that properly.
Except even locally time is different for different people. People work nights, mornings, afternoons. Some shops open at 6am, others at 9am. Some people get up at 5, others and noon.
You still learn that x time is your time to do y, and people will quickly adapt to whatever number x happens to have.
We only associate 9am with anything because we learned to. We could just as easily learn a different number, and people with different work schedules do just that.
> Except even locally time is different for different people.
If you say "9pm local time", everyone knows it's the evening no matter if it's the time you go to bed or stand up because you work the night shift.
If a book says someone slept until 1pm you now they slept until mid day, no mater where the story plays. You don't have to go to the internet and look up if where he lives 1pm is morning, evening, night, etc.