As long as you have the very concept of "local time" you are going to run into some form of the problem where it is difficult to interpret what local time is and how it relates to other times. DST is just one possible difference
As long as you have the very concept of "local time" you are going to run into some form of the problem where it is difficult to interpret what local time is and how it relates to other times. DST is just one possible difference
In your original post you said "we designed our culture around calendars and clocks, synchronized to Earth revolutions". For me the driving principles of modern time systems seem to be (and I think this might align with what you said)
- each day should have the same length
- people who live or work near each other should agree on the time
- the time on the clock should correspond to the position of the sun, locally
All three principles are important, but the third definitely takes a back seat in many places/lattitudes.
You seem to be suggesting the third should be the most important. Do you think the others are important as well, or are you suggesting that we change our culture so that they are not important to us anymore?
Agreeing on location data is relatively easy (with day-to-day precision), because we have well-defined units of distance and reference points. Agreeing on time is likewise difficult, because we have neither: both length-of-daylight and start-of-daylight tend to vary by location and time (heh, recursion).
The time on the clock (the way it works today) cannot really correspond to position of the sun: the further you stray from equator, the less defined this relationship becomes, until you cross polar circles where this relationship breaks completely. People agreeing on time *only* locally is not really helpful with close international relationships.
Essentially, there is no good way around this. Time references like "at sunset" or "a year from now" are just not universally defined. We could base our time references on universally coordinated time which would require local time reference adjustments (work starts at 8:00 in location A, but at 13:00 at location B), or we could keep time references consistent in local, but adjust the meaning of local time. It is the same in the end - you need some logic and context to work out what "at sunset" means.
And this is my gripe with anti-DST. DST is not problematic. If anything, DST is easy, because DST adjustments happen in large chunks and therefore errors in DST handling usually become apparent quick. What if we did DST in 1 minute increments and northern regions had a total of 6 hours DST shift? It would be much harder to spot handling errors, but the underlying mechanism would still be the same.
The problem is not clocks or timekeeping itself, but rather how we communicate and synchronize what an ill-defined time reference actually means.