[Johnny555]

No it wouldn't -- users of your applications will still want to see "human" time in different areas, so rather than a (relatively) well defined Timezone standard, you'll need to keep a table of accepted working hours, meal times, etc for each region.

At least now you can tell them that it's 5pm in their selected area so they can decide what that means.

[gt_]

This is the exact problem it would solve, once "everyone" had actually switched.

[Johnny555]

How does it solve anything?

If everyone was on UTC and I want to schedule a meeting with my coworker across the country, I still need the application to tell me what time standard business hours are wherever he is located

So the developer still has to do the UTC->Localtime lookup.

Plus, when I travel, I have to keep a chart of local "human-time", so I know that when it's 03:00, it's time for lunch.

[zanny]

You always have to ask the question "what times are good for you?" because everyone lives on a different schedule.

With global UTC it just means the times each of you give don't need to go through a complicated conversion process to interpret.