851–860 of 1001 posts
I'm surprised at the number of commenters who think permanent DST is favourable to night owls and bad for morning people. I think it's night owls and delayed-cycle teenagers attending school who will suffer most under permanent DST. In the Winter, permanent DST means everyone has to get up an hour earlier for work or school's clock time, relative to the sun which regulates their body rhythm. Someone pointed out virtu…
There's no disinformation campaigns to worry about, nobody getting 'cancelled' for their poor arguments on the topic, no fraudulent studies being passed around. At least, for the time being...
I think I can say this on behalf of most developers who have ever had to fix DST errors in their code: Thank fucking god. I am shocked that none of our unit tests failed on Monday. One of the first code reviews I did here I pointed out that his tests were going to break in a few months when DST kicked in because his tests asserted that there was a 24 hour gap between two calculations. He responded this code was tempo…
I am extremely surprised at all the people who are against this, saying that "Making DST permanent forces people to wake up earlier." I am not sure I know a single person whose morning wake-up time is dictated by the rise of the sun. Everyone I know wakes up whatever time that their work tells them to. I am happy to have more sun after I get out of work. It was a breath of fresh air this week getting out of work and…
My personal pet peeve is when people write the Standard Time acronym when scheduling cross-timezone meetings, despite the fact that it is Daylight Saving Time. (Eg. "I'll call you tomorrow at 4pm PST.") In the past, I've gotten paranoid that they may live somewhere that doesn't observe Daylight Savings, but I also don't want to seem like a pedant by bringing up their mistake. I'm curious if this change will make this…
I've never known anyone who wasn't a programmer who even knew the difference between say, PST and PDT. Like, if they didn't schedule it through a computer with up to date timezone code, I would confirm verbally.
Someone with experience dealing with this needs to write it.
I'd kill for a peek into the parallel universe where it was permanent standard time that was likely to get adopted and see how much effort went into researching the ill effects of that choice to convince people with enough FUD to keep daylight time switching going. Here's the thing: If you're a proponent of permanent standard time, you should be in favour of turning off the switching no matter what. Even if it means…
You don't need to kill anyone. You can just travel to AZ or HI, neither of which changes their clocks for DST.
I'd kill for a peek into the parallel universe where it was permanent standard time that was likely to get adopted and see how much effort went into researching the ill effects of that choice to convince people with enough FUD to keep daylight time switching going. Here's the thing: If you're a proponent of permanent standard time, you should be in favour of turning off the switching no matter what. Even if it means…
Agreed. The posted decision (permanently DST) is stupid, but less stupid than switching.
I think I can say this on behalf of most developers who have ever had to fix DST errors in their code: Thank fucking god. I am shocked that none of our unit tests failed on Monday. One of the first code reviews I did here I pointed out that his tests were going to break in a few months when DST kicked in because his tests asserted that there was a 24 hour gap between two calculations. He responded this code was tempo…
If this law will solve your problems then I … guess your code doesn't have to work outside the US?