The article: https://www.politico.eu/article/norway-arctic-region-asks-eu-commission-for-26-hour-day/
How would the new time zones work in practice? Wenche Pedersen, the mayor of Vadsø who authored the letter, is unsure.
“We haven’t thought a lot about that” she said. “The clock will go from 12 to 13… and we have to see how this will go. I don’t think they’re going to say yes so we haven’t thought about all the details.”
Huh. Great idea.
Make a proposal without a plan or a feasibility study is peak management. Starting to understand how I end up with projects with very firm deadlines that are only vaguely defined and no one is sure if we have the resources on hand.
I hear they’re also declaring that pi equals three.
Or 5
Seems like these idiots have too much time on their hands already.
I’d start with a 13 month/28 day calendar and planetary time (all clocks set to UTC).
EDIT: And set the date format to YYYY.MM.DD for the entire world. Americans and Europeans can stop arguing. The Japanese got it right.
If you’re not using tz_database or equivalents for literally all date-time logic, if 24 or 60*60 are constants defined in your project… you’re doing it fucking wrong. I don’t know how many times we need to break out the idiot club, but date, time and timezones are extremely complicated - unless your business is primarily concerned with them you must use a library or service.
Do Not Reinvent This Wheel
What does tz_database do? Wikipedia makes it seem like it basically converts a pair (geocoordinatr, utc time) to local time
From my very basic understanding, yeah that’s basically what it does. However it accounts for a whole lot more into adding or subtracting from UTC. Timezones aren’t absolute, they’re political. Timezones have weird rules, and history that needs to be somehow expressed in the code to get the right time. That’s what’s sets tz_database apart from just looking at a map and saying it’s +7 UTC.
So it updates now and then with new rules, and it keeps historical rules for past dates?