this post was submitted on 07 Oct 2024
1118 points (99.4% liked)
People Twitter
5089 readers
1768 users here now
People tweeting stuff. We allow tweets from anyone.
RULES:
- Mark NSFW content.
- No doxxing people.
- Must be a tweet or similar
- No bullying.
- Be excellent to each other.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I’ve never heard anyone who likes DST… this thread confirms my bias. Arizona has it right. We have internet now, no need to change clocks, just update your schedules for the season.
I like DST. I just don't like changing the clocks. Permanent DST would be the ideal imo
I disagree. The sun does not need to be up at 9pm in the summer. We have light bulbs now.
Eliminate DST entirely, and call it a day. Like the other person said, Arizona has the right idea. Let's do permanent fall/winter time. People who live in far north regions like Alaska, Iceland, Norway, etc can go to permanent DST if they want. But it doesn't make sense for most of the world.
I'm in one of those more northern areas so maybe that's why I prefer DST. In the summer the sun is up so early and sets so late that it doesn't matter, but in the winter DST would mean at least some evening light when more people have free time than dark at both ends.
Iceland here, we don't use DST at all. GMT / UTC all year round, it's nice.
There has been a lot of discussion in the past few years about adopting it though, but a lot of people don't really see the point, me included.
During this time of year, October / November, the days start to get really short, so the sun doesn't rise until 8 or 9, and it sets around 16 to 18.
Having some sort of DST here wouldn't make much sense IMO since it would only be 3 months or so. Then there's the debate of do you want to use DST and have the sun rise sooner, but set sooner or vice versa with no DST.
Personally I like that the sun is still somewhat there when I leave work, since even with DST the sun would just barely be starting to rise when I would be commuting to work in the morning.
(Tangent: I don't get why a lot of global schedules for some events list the start times of a live stream for a ton of different timezones, but never also include just GMT / UTC)
I'm in Canada and I just don't want it to get dark at 3PM. That's why I like DST
They tried that for a year or two in the 70s. Everyone hated it.
Who is "they"? Also, most of the world doesn't have DST and they seem to be doing okay.
The US at least I think some of Europe was involved, and that's what I was saying. We tried full time DST and it doesn't work.
"Everyone" hates the status quo, too. And I bet if we made it standard time year round, "everyone" would hate that.
To clarify, they hated it enough to change it back to switching twice a year.
I don’t like DST, but I hate what Arizona does most. Driving through there and hitting that damn bullseye and wondering what the fuck is going on with my clock. Especially since national parks don’t observe dst, and Arizona is on a time zone border so really it switches between sharing a time with New Mexico and with Nevada/California. And Indiana isn’t off the hook for the same crap.
I would go one step further, just get rid of timezone completely and just get up at different times depending on where you are on the planet.
Please think how confusing this would be to talk to your overseas friends. It doesn't actually solve the issue, just pushes the confusion into a different metric that is also hard to track. People in 23/24 time zones will also have a "different" schedule to adapt to.
"It's 10AM here. What time is it there?" "Also 10AM." "Oh. Um.. the sunrise is at 7AM here, so 3 hours past that. What about you?" "Well, the sunset is at 5AM here, so it's almost bedtime." "Let's meet tomorrow night then." Do you mean when the clock says PM, or when it's physically dark here?"
It's a contrived example because you wouldn't ask "what time is it there?" in a world where everywhere uses the same timezone
But you would ask “what are the work hours/sleep hours there”
Or, more likely, when can you be online/when is your business open/...
Yes. That's the point. What question would you ask otherwise? Because it's not a standard question that exists right now.
It's introducing a new concept that's just as confusing, but without a common reference point. "When is day for you?" "What's your light schedule?"
If you want to use a single time for everyone, we already have GMT, no one uses it for daily use because it's obtuse as hell if you don't live within an hour or two of it.
Not the original commenter, but why couldn't it be more like "John sleeps from 12-20:00 and is usually working from 21-5:00" and "Stacy sleeps from 8:00-16:00 and works from 17-1:00", so Stacy and John decide to plan their video call for 6:00-7:00? Like I don't super care what light schedule it is, more what my friends schedules are specifically, right? And the question could just be, "What times are you available?"
You're forgetting about days of the week, which would change part-way through the day now.
"Are you free on the 18th?"
"We'll, we start work at 20:00, so are you taking about the 18th from 0000 - 0400, or from 2000 - 0000? Those are two different days for us."
Oooh, fair point. I do think that's still tricky now (I work with an international team) but it definitely wouldn't get any better
EDIT: WAIT unless the date switched over at 00:00 every day no matter where you were
It would be annoying to be the many people whose work or waking hours were on "MonTues" though lol
Even better would be the various laws relating to things that are geographically bound.
Labor laws for teenagers over 16 typically state that they can't work during the hours of 0700 to 1500 Monday through Friday, 2200 to 0600 Sunday through Thursday, and 2330 to 0600 on Fridays and Saturdays during the school year.
Imagine the nightmare of what that all turns into when day change happens in the middle of those blocks of time.
A lot of labor laws and accounting in general become terrible.
8/24 time zones, or 1/3rd of the planet would deal with that at work.
Just put them in the pacific ocean.
Same question I asked Kusimulkku: do you not even know anyone who works second or third shift? Because we ask eachother about specific sleep schedule times all the time, ie, its a very standard question for most working people.
I used to work both.
With universal time, the answer is meaningless without also knowing where they live. If you have a friend who is traveling and says "Oh man, I stayed up until 3AM last night." Did they go to bed early or late? Not only do you have to clarify their normal sleep schedule, you also have to figure out where they currently are before "3AM" has any relevant meaning.
It's objectively worse for communication. As I've mentioned to other posters, we already have GMT if you want to use that. Let me know how well people understand you when using only GMT for scheduling.
I'm glad GMT exists as the middle point for us to use personalized time zones, but don't want to lose that "midday" is when the sun is high in the sky and "midnight" is partway through the dark time.
Basically you have several scenarios:
and several topics you could talk about
Assuming any initial adjustments to new systems are ignored for the purposes of the next paragraphs.
Any system is really not a big deal for local communication since everyone knows which hours are sleeping hours and which season it is (day length,...).
Communication with people on the other hemisphere uses the same times, except when DST fucks it up, sometimes at different changeover dates and in different directions if both use DST. Day lengths, sunrise/sunset, temperatures,... all differ and are not really comparable unless you mentally apply a six month offset to your own experiences.
Communications with people far away in west/east direction requires knowledge about the timezone offset, sometimes half hour or 15 minute offsets, as well as potential DST changeover dates and if they use DST at all. Every time you want to schedule anything you need to mentally convert that time to either something like GMT/UTC you use for scheduling or to the other person's schedule. If you have a regular event that happens at time x every week DST changes can make it change up to 4 times a year if both places use different DST changeover dates.
Day length and what is sunrise and sunset only really work without problems if you live at comparable distances from the equator, temperatures are influenced by things like the gulf stream and other weather patterns and geography (nearby oceans, mountains,...) in addition to the day length. So you have to figure out more details here anyway.
So basically you can communicate about any of that stuff clearly just based on assumptions in the current system mainly with people who live in the same place as you do or with people who live in a geographically very similar place that observes the same DST rules yours does and is the same distance from the equator assuming the other person has a similar sleep schedule as you do.
And the cost for that is that anyone who ever wants to schedule anything with someone who lives a bit further away has to do some mental gymnastics and know a lot about the system of timezones and DST for everyone involved.
"Did they go to bed early or late?" ... they went to bed x hours ago. If anything, the math is easier when your 3am is also their 3am(although am/pm would also have to go out the window). Time-zones or no doesn't tell you when they got up or started working without you asking either.
What if the story is from a week ago? Yes, your 3am happens at the same time as their 3am, but your 'night' is still their 'day'.
You'd have to intuitively know every time zone and their offset in order to have an immediate understanding the way you do now that 3AM is the middle of the night. It requires an additional question or lookup table, which makes it objectively worse of a system for humans to use and remember.
"what time is it" is the natural way that people have asked about where in the typical day night cycle it is for eons. We don't really have another way of formulating the question that flows naturally.
It would be the same time everywhere, but you'd only know what that meant in places you were familiar with. Otherwise you'd have to look up the difference in a big table, which is exactly what a timezone is.
We have a system for a uniform clock that's synchronized everywhere on the planet. The people for whom it has benefits already use it.
So instead of looking up what time it is somewhere, you'd have to look up their local offset and mentally recalibrate what all the numbers mean in relation to time of day?
That sounds an awful lot like timezones. I already do this when I'm in a different timezone or when someone else I know is.
Why do you even need to know what the numbers mean in relation to time of day? 99% it is completely irrelevant whether someone is unavailable because they are asleep, at lunch, at dinner, (not) at work,... but just when they are or are not available. Or you just want to communicate an event and that event happens at one time and everyone considering attending it just has to convert it to their own timezone now.