Sorry but that is just crazy. TBH the change of clocks is a pain, but we all cope with it. So some reasons not to fuck about:-
- Unless we make working days shorter it will be dark one end or other of the day in winter. That is tough. Changing the clocks does not make more daylight. Darkness causes accidents and problems, but tough. This won't be solved be renaming the hours of the day - it will just move the issues around.
- Changing clocks is a pain. I have spent a lot of time on software development related to this in every system we have in the company. Man months of time spent/wasted to allow for clocks changing. But we cope. We have systems that understand 23 hour days and 25 hour days. We do better than some (BT!) in sending correct times on XML messages. It would all be a lot simple if clocks did not change.
- But clocks not changing does not mean UTC+1 for the year - that really is fucked up. When the sun is overhead in Greenwich the time is 12:00. That is the way we decided to name the hours of the day. It makes sense - it is the middle between one midnight and the next. Living in UTC+1 in the country that defined the clocks in the first place is just madness.
- At the end of the day, what we call the hours is not important. If we think there is a benefit in people going to work and school earlier, why not do that. You do not have to change what we call the hours of the day. Yes, it would not be universal. Make schools an hour earlier and some offices and shops will follow and some will not - excellent. It would spread out rush hour on the trains and roads. That alone means fewer accidents and problems.
TBH I bet I have a lot of code that will in fact break if we were UTC+1 and no DST. It would cost me to make that work, and I am a small business. Imagine someone the size of BT changing all their systems to handle that. We are lucky we are based on UTC as lots of stuff is hard when not on UTC. DST is a problem, but UTC+1 all year would be a lot more work.