[Beanis]

If you live up north, adjust the local schedule instead of the clocks. If kids are waiting in the dark, move the start time to later in the day. If it is light out at midnight shift your schedule so you go to sleep after 12:00am. If you are living your life based on the position of the sun, the numbers on the clock are going to mean something a little bit different everyday anyway.

Time is supposed to have a relatively consistent meaning, and we jump through a lot of hoops to give it an inconsistent meaning. Schedules are much more fluid and easy to change with little external side-effects.

People will need to learn to partially decouple their routine from the numbers on the clock, but that seems like a much simpler/cheaper problem to solve than our current time mess.

[robmcm]

That would be ideal, if everyone worked on GMT and just started work at different times, rather than the same time in a different timezone.

Technically we could all do that now anyway, just start using GMT rather than our local timezone :)

[phpnode]

Can you imagine how much more difficult that would be to program for? Instead of (relatively) easy to parse timezone rules you have some kind of awful, locale specific agreement that that event you scheduled for 9am monday every week would actually occur at 8am half of the year?

[Beanis]

I'm not sure if you are serious, but I don't understand what you think would be involved. If you remove the time inconsistencies from a calendar, any decent calendaring app will solve the scheduling problem you are left with. Scheduling is a data entry problem. It is a problem we have with or without timezones and dst changes.

[robmcm]

We actually used to do this at school, where in the winter we moved sports to be after lunch and then had afternoon lessions at night.

We basically had a summer and winter timetable.