More importantly the US should switch to the metric system.
Like your arguments against changing the calendar to something more rational are the same arguments a lot of US folks use to justify not switching to the metric system.
Well played.
https://www.nist.gov/pml/owm/metrication-law
15 USC § 205b
Why switch to a system that is widely agreed to be worse for normal human communication than the one we have.
Fahrenheit is far superior of a system, where 0 to 100 roughly reflects the range of temperatures one might expect in the lower 48. When you are outside that range, you know you’re in for very uncomfortable weather. Celsius doesn’t give much benefit beyond the vague water will freeze around 0.
And then we get to distance. The US has a system where a foot is divisible by 2, 3, 4, and 6. Metric is only divisible by 5 or 2. It is horrid if you need to divide things in thirds.
Hell, if you've got something 2.4 meters long and 7.87 ft long, it's the metric length that happens to be conveniently divisible by 12.
The situation with machine tools in the US is unbelievable, by the way. So many stupid mistakes have been caused by the confusion between mils (1/1000 of an inch) and millimeters. And many many tools and bits are designated in fractional inches rather than whole or decimal units (as in countries using metric) which is a massive pain in the ass because both CAD software and quick mental comparisons are generally not conducive to bizarre fractions like 9/64".
Machining is different, and metric is accordingly often used there.
This does not sound like you’ve done much of either. I spent my summer rebuilding my kitchen and, oh boy, do millimetres matter.
To be fair, this wouldn't be an issue if we had only imperial units. It's only possible to mix these up because we have an awkward mix of both systems.
> The situation is legitimately a little bit different with minutes and hours, since we are able to specify units of time somewhat arbitrarily to match the units, i.e., if hours were 64 minutes instead of 60, many meetings would instead be 64 (or 32) minutes long.
The same situation is true of carpentry, though. when we're building something out of wood we rarely have specific dimensions we must meet, we're building something artificial and can pick the closest round number. 2x4s are 2" by 4" not because they need to be slotted into some naturally-occurring fixture but because it's a nice round number that is sufficiently useful. The standard ceiling height in the US is 8' not because of any law of the universe but because it's a round number that's easy to measure and easy to divide (quarters, halves).
Your examples of something 7.3 feet long or 7.87 feet long simply don't come up in carpentry because we'd usually just round up to a nice number and scale the whole project accordingly. And if we do have something that needs to be precise within +/- a certain tolerance, a base unit that is easily divisible is more likely to be able to round conveniently while remaining within the tolerance.
Too large and you just can't get the screen into the frame, and too small and it can just fall out, or at the very least leave gaps large enough that bugs can get through.
I agree with you that there are many things where we don't have a specific physical need for certain dimensions, so we just pick round numbers. But I think the cases where we do have to conform to some messy existing physical dimensions come up more frequently than you think.
Would Americans love pre-decimal British currency? All those shillings and florins with lots of integer divisions? I bet the average metric hating American would be unironically demanding decimal currency back when faced with it.
I always get curious about how American construction works when I hear this argument. Do builders spend all their time dividing stuff into 3 rather adding, multiplying or subtracting? I would've thought adding a sequence of measurements up would be a far more common operation.
What happens when you need to divide something into 3 a second time? Or you need to divide an arbitrary length into 3? Or what if you need to divide into 3 sections, but there is something extra between each section (like a frame or a post), or you have to account for the width of the cuts etc?
Is an 8x4ft sheet (eg plywood etc) really easier to mentally divide into 3 (on either dimension) than a 2400x1200mm one?
I'm Canadian. I deal with a bastard mix of metric and imperial daily. Farenheit is the one unit I've never needed to learn in the slightest. I can deal with lbs, feet, inches, etc.
As for claiming base 12 is superior because you can divide by 3, what happens when you divide by 10? Surely if base
Which is... Pretty random? What is "very uncomfortable"? 'Switch to autumn/spring clothes' uncomfortable (<20ºC)? 'Switch to winter clothes' uncomfortable (≈0ºC)? 'Get a sweater below your winter clothes, and maybe double trousers, too' uncomfortable? (<-20ºC)
Celsius fits the mental model of normal human communication quite well if you use it.
> Celsius doesn’t give much benefit beyond the vague water will freeze around 0.
Which is a very major shift: rain turns into snow, roads get slippery, you should dry your hair extra-carefully (> 0ºC it's raining anyway, you'll get wet anyway, why bother; <0ºC it will turn to ice on your head, you definitely don't want that).
Water freezing is a VERY major weather shift.
That last bit is the key: Fahrenheit also fits the mental model of normal human communication quite well if you use it.
The F vs. C wars are silly; if you were raised using a particular unit system, then that system will most likely feel the most natural to you. If you didn't, you can certainly learn another and adapt, but for most people it won't feel right.
This is all just fine. Yes, it's annoying when you travel to a place that uses a different unit system than you're used to, but life is full of such things, and we should just live with it rather than trying to argue what's "right". Nothing is right, nothing is wrong. Whatever is, just... is.
(Note that I'm not making any arguments about which one is better for math or science or whatever. Just about what feels comfortable. For the record, I do think many things -- including global interop -- would be easier if we all used metric. But I don't think, no matter how hard I try, I'll ever be able to "feel" celsius properly.)
Water freezing around 0 is a good indicator that the temperature is cold enough to kill you given that you're mostly water.
If I'm dividing a length of wood in thirds, I use my metric ruler, and I mark out three even cuts. It's crazy how they sold me a 2x4 in feet and it still divided into centimeters.
Widely agreed by whom? Because the rest of the planet thinks otherwise.
A foot is 12 inches, a yard is 3 feet and a mile is 1760 yards. And don't get me started on the weight and volume units.
I entertain a hypothesis that such inconsistent unit systems (and heavy usage of fractions instead of decimal or other positional system) do make people less apt in handling numbers. Having lived for a while in England (which is legally metric but in practice imperial for many things) for a while, I think it is reflected in how things involving numbers are often stated in quite convoluted terms.
First, 0 and 100 F seem completely arbitrary.
Second, if they have such immense value, people using centigrade could manage to remember "-18" and "38."
My brain is sadly stuck on the default "F" units since I grew up in and continue to reside in the US, yet even I can remember general mappings of Centigrade to "how it feels" as a human. This is not a difficult thing to do/learn.
Other factors (sunlight, wind, humidity) make that level of precision kind of useless for a "how does it feel" situation, which IMO just further degrades the value of 0-100F thing as conveying any particular significance.
The 1st would always be a Sunday, the 25th would always be a Thursday, etc.
Sure, celebrations can still be held on weekends, but it’s just not the same. And Fri 13th would die away.
What's so frustrating to me is when I realize that, for example, public holiday falls on the weekend (I know this is solved by some countries by moving the holiday to Monday or Friday). Last year, 24th of Dec was a Saturday, pretty much the worst time for Christmas.
I guess we don't need to move them because we have plenty anyway, compared to the few ones the Americans have.
Heck it's not even weird to not bother with this redefinition and just have a party on a more convenient day.
(My birthday falls on a national holiday where I live, though, so in practice I've never had to worry about school or work on my birthday.)
Friday and Sunday get different names, unrelated to Sabbath as far as I can tell -- paraskevi and kvira.
Lots of influence from Greek culture in Georgia for sure. For a fun fact, the Georgian for "Greece" is saberdzneti -- the land of the wise. Berdzeni itself means wise (as well as Greek), but I'm not certain if it's derived from an alternative historical name for the Greek.
[1]: https://www.etymonline.com/word/Monday
Edit: also wikipedia https://en.wikipedia.org/wiki/Monday
https://www.vikingeskibsmuseet.dk/en/professions/education/v...
(FWIW, I agree that Monday is the second day, but mainly just because that's what I was raised to believe. Plus if Sunday is the end of the week, that means Saturday isn't a weekend anymore, which is nonsense.)
Segunda-feira (2) = Monday
Terça-feira (3) = Tuesday
Quarta-feira (4) = Wednesday
Quinta-feira (5) = Thursday
Sexta-feira (6) = Friday
Sábado = Saturday
Domingo = Sunday
The weak parity didn't prevent a friend from booking a rental car in April although we were going to be in the destination city in July.. the days of the week matched!
Why would it affect you? Presumable like 99.9% of all humans you just use some sort of library to handle it all for you anyway... hell that's a practice older than programming (a physical API called "calendar").
Having a null or two a year sounds quite nice frankly... and if it makes scheduling any harder than now, that's a benefit. Just make it a day off for everyone but the most essential people (medics, law enforcement, etc, and just pay them double for the day if they work on null day) like holidays used to be, but we (tech folks) could actually help enforce it by having those special cases handled by hardcoding.
Someone who administered a scheduling system for flight crew was telling me how hard it is. Multiple time zones, contracts, unions, jurisdictions, companies and staff roles (which require frequent recertification) etc.
Imagine handling a bonus day in this context. It does not sound good.
In the middle of Europe (Paris, Berlin) the time the sun is visible varies by over 5 hours, and if you go further north it's even worse. Where I live it is already dark when I leave work at 5pm. Three months ago, it was brighter at 10pm.
Many regions have timezones that are too big. In Europe at the east of the CET timezone the sun rises at 6:36. At the west it is 8:16 - nearly two hours difference!
China is even more extreme, although they have one time people in the west of the country start their days later, so if you are in the office at 8am in Beijing, although it's 8am in western cities too, you don't know if people are in the office or not. At that point timezones have lost thier value, as you can't use them alone for scheduling.
You answered your own question in the following sentence - ISO 8601 timestamps do not require a time zone, and infer "local time" if none is provided.
For this reason, most people either use UTC time or they use offset timezones for timestamps. The latter is nicer for humans who like understanding when things happened in terms other than hundreds of millions of seconds since 1970, but more complex to implement.
Using standard ISO timestamps is good. The reason why people would like to use them is because they sort well, they parse everywhere, and they're human-readable. That last reason is the main and really only reason why you would prefer it to a Unix timestamp. They're standard, but they're a standard for how to communicate things in a human-readable manner. If you wanted to just store accurate time, store a binary 128-bit fixed-point long instead of using UTF-8, since it doesn't need to be human-readable.
> [5.3.1.1] When the application identifies the need for an expression only of a time of the day then the complete representation shall be a single numeric data element comprising six digits in the basic format, where [hh] represents hours, [mm] minutes and [ss] seconds.
> [5.4.1] The components of a time-point shall be written in the following sequence
> For calendar dates:
> year - month - day - time designator - hour - minute - second - zone designator
> The zone designator is empty if use is made of local time of the day in accordance with [5.3.1.1]
[1] http://lists.ebxml.org/archives/ebxml-core/200104/pdf00005.p...
I think this sort of argument is a bit shortsighted. Using ISO timestamps brings with it the semantics of including UTC offsets in pretty much every operation and historically date library APIs have had their ways of confusing consumers. Sure you can read the data without having to convert them in troubleshooting. You also will end up troubleshooting more because somebody somewhere used a library call that discarded an offset or something similar.
> While it may be safe to assume local time when communicating in the same time zone, it is ambiguous when used in communicating across different time zones.
https://en.wikipedia.org/wiki/ISO_8601#Time_zone_designators
> So the zone designation for New York (on standard time) would be "−05:00"
Except for the other half of the year where it is "-04:00". If you, by chance, pick that offset up in logic, make sure that where you apply it it is still the same half of the year! Classical off by one.
Most religions deal by having their own religious calendar. They the civil calendar is the Christian one is not a requirement.
Visionaries at companies like Google and Apple are known for their "ugh, special cases!?" approach to not finishing Jira tickets, which is why they are where they are today.
A week means 7 days.
Every month is 4 weeks long, or 28 days long. (I'm not sure how it handles leap year.)
I was thinking to myself I liked this idea until I saw this. So there are days that now do not belong to a week. I cannot imagine how much special casing this would require.
> “A ‘month’ does not mean anything,” they wrote. “A day means something. A year means something. But a month?”
Then by the same logic the week needs to be abolished. Then the problem above wouldn't exist. Now tell that to the religions.