DST, on the other hand, pushes daytime later, so if you wake up at say 8 (after sunrise for most of the year) and go to sleep at midnight (after sunset), you see more daylight.
DST, on the other hand, pushes daytime later, so if you wake up at say 8 (after sunrise for most of the year) and go to sleep at midnight (after sunset), you see more daylight.
In some countries, even to +/-15 min - Russia comes to mind.
Edit: downvoted for asking people to go up at another clock time in order to match the daylight, instead of going up at the same clock time and changing the clock to follow daylight.
Really? What's so important about the number on the clock? Why not just be consistent with daylight, and let the clocks be normal?
Because jobs, business hours, travel schedules?
Why again does people want clock time not to match solar time? It's far more sane to change the numbers on the schedule than to change the clock.
Making DST permanent "just" requires a singular change of legislation, and basically never switching the clocks back to "normal" time.
As has already been stated twice in a sibling discussion here, "changing an entire culture is hard", but I'm honestly interested in hearing your approach.
It's ridiculous to suggest that it's easider for every business update Google (and Yelp and everything else) twice yearly, and that everybody check that before they go anywhere. That is way more human labor than daylight savings.
In fact even my regular calendar app can support this but itself, it can notify me of changes in booked appointments automatically.
And even that's assuming you didn't already know the change in schedule because it was listed right there on the website.
Currently, clocks automatically change twice a year.
In your proposal, all schedules for businesses, schools, transport, etc need to be entered into multiple online services. Plus each person needs to use one of those services and tell it about all of their plans. Then they need to be notified by that service whenever anything changes, and when hours change in a way that's conflicting, they need to manually resolve that.
As an example, I was just talking with someone who has to pick up kids from two different schools; the route involves two different transit systems. All work meetings must be carefully scheduled to match, and there are inevitably errands that will involve zero, one, or two kids and getting to some place before they close. This is hard enough when hours are stable. Now imagine it with schools, transit systems, stores, work clients, and work vendors all potentially adjusting operating schedules 2 or more times per year.
Google Now can't do that, and probably won't before the Singularity.
Convention.
You may not like it, you may not understand it, but other people like their conventions, and you're simply in a tiny, tiny minority if you don't get that.
"Hi, our family's switched from observing the clock, like everyone else in school, to operating on a schedule that is in rhythm with the ebb and flow of sunrise through the year. From now on, we'd like our kids' school attendance and lesson times to start and finish on a solar timescale. Perhaps a separate buzzer tone could be set up to convenience any kids who will be running their day according to the sun. We do understand the challenge to teachers in accomodating this natural schedule alongside other students who stick with the more familiar clock-based one, but hey - the sunlight is the convention we follow."
I mean I live in quite a hippy place but that just ain't gonna fly.
Clocks are standardized, which means there's a simple point of coordination for fixing them.
Schedules are...not.