11 ms·
The real advantage is that Azure and AWS and every other US-centric cloud service insists on showing me that something happened on the 3/11/2021. It's a wild g
by jiggawatts 6y ago
The real advantage is that Azure and AWS and every other US-centric cloud service insists on showing me that something happened on the 3/11/2021.
It's a wild guess to figure out if that is the 11th of March or the 3rd of November.
Unless there's also another date with a number higher than 12 in it, there is no way to tell. None. None whatsoever.
For US staff with US regional settings, it's always obvious which date is correct. That is the one single case where there is no confusion. This works as expected for just 4% of the world population, but it is those 4% of the world that get to decide the date format.
It's the most obnoxiously American attitude imaginable to ignore this issue because it doesn't affect them... only the other 96% of the planet.
/rant over
- vbezhenar 6y agoIt took many decades to widely adopt UTF-8. I think that one of the reasons was that US companies did not really care about character encodings, as it's not something they have to often deal with. Even today managing multiple keyboard layouts is a pain in most operating systems, it's buggy, it does not have enough configuration options, it's not convenient. Probably because most US developers never tried to use that functionality.
- jacobolus 6y agoMac Firefox and Mac Chrome both break a bunch of keyboard shortcuts if you use a non-US-ANSI keyboard. Safari handles alternate layouts correctly. Just yesterday I learned that on an ISO Spanish keyboard, both of those browsers will pop up a help menu for ⌘⇧7. The logic goes: ⇧7 means / on a Spanish ISO keyboard, and ⇧/ means ? on a US-ANSI keyboard, therefore ⌘⇧7 is by the transitive property of inter-layout shift functions equivalent to ⌘?, which is the shortcut for opening the help menu. They don't pop open the help menu if you press ⌘⇧', the actual ISO Spanish layout way to type ⌘?
- misterS 6y agoStuff like this is the reason why I, as a non-american software engineer, use `US_en` layouts on all my machines.
- jacobolus 6y agoI use a Japanese keyboard that pretends to be a US-ANSI on my laptop. The extra keys and narrow spacebar are super handy. Something like http://www.keyboard-layout-editor.com/#/gists/9150730dbd4d2824ec3cca5b62925f38 http://www.keyboard-layout-editor.com/#/gists/9150730dbd4d28...
- SwiftyBug 6y agoSame. When I have to use someone else's computer without an US_en keyboard I look like an elder learning to type.
- Semaphor 6y agoI use EurKey [0] (I think this was actually recommended to me on HN) so I have easy "AltGr" access to German characters like öüß. Sadly some tools (most notably Microsoft’s) have hardcoded shortcuts for some of those, which is really annoying. [0]: https://eurkey.steffen.bruentjen.eu/ https://eurkey.steffen.bruentjen.eu/
- trinix912 6y agoI use the Canadian English layout on macOS for most of the time, if I need to enter accented letters, I can just hold down a normal letter (A) then select an accented one from the popup (Å). The international English layout works the same way if I remember correctly.
- lou1306 6y agoNot only Firefox. Cmd-/ is also a very common "toggle line comment" shortcut. I think it's the default on Sublime and IntelliJ, and any editor that offers a "Sublime compatible" preset (like VS code) imitate that. Of course, such a shortcut broken out-of-the-box for any keyboard layout that lacks a / key.
- jacobolus 6y agoYeah, Sublime copied this shortcut (like most of its features) from TextMate, and it has since spread widely. Amusingly, TextMate's author and many early users were European programmers with US-ANSI keyboards (because the various European layouts are just too painful for writing code in ASCII-based programming languages).
- happymellon 6y agoMac everything breaks for me on a UK Mac when using an ISO keyboard rather than their non-standard ISO layout. Page down only sometimes works, and Command+~ to switch same app Windows works in some apps and not others. It's a bit of a train wreck when you want to get rid of their pointless keys.
- trinix912 6y agoThe built-in apps seem to handle it pretty well (ex. the dictionary app has ⌘Ä / ⌘Ö shortcuts when set to Swedish). 3rd party apps often don't care and it gets worse the more you move away from plain QWERTY. Although macOS is good in the aspect that combinations akin to AltGr on PCs aren't unique to non-US layouts. I've seen programmers assume it's safe to assign shortcuts to Ctrl-Alt (which simulates AltGr), making it impossible to enter certain characters. Not surprising, as it's not used on the US layout (just as there's no extra key next to the left Shift).
- young_unixer 6y agoAnd multiple languages. Spell-chackers enabled by default are specially annoying.
- fauigerzigerk 6y agoBut contrary to the date issue, you could at least make a case for using ASCII everywhere. I'm not saying it has no downsides (e.g information density). It may also be unrealistic and culturally insensitive, but there are very clear upsides as well. Not so with the U.S date format. It's just bad.
- mmis1000 6y agoUntil people get used to emoji... And not supporting UTF-8 is suddenly a big problem even for English people now.
- SwiftyBug 6y agoMy wife recently bought by mistake a keyboard whose layout I couldn't figure out. It took me a full 5 minutes to even get to the correct place where I could configure keyboard layouts under Windows 10 settings. Then I had to choose the keyboard layout I wanted to add. This was a list in a dropdown with hundreds of options without an image of what each layout looks like so I could not check which option matched the keyboard in front of me. There was not even an input field where I could test the chosen layout, I had to switch back and forth from the Notepad. After many tries, I finally got it right: Portuguese. Completely by trial and error.
- majewsky 6y agoI like the method that Mac OS uses to detect the layout of a newly connected keyboard. It brings up a dialog asking the user to press specific keys (something like "type the | character") until there is only one possible layout that would generate the observed keycodes for the characters in question.
- bombcar 6y agoIt’s really well done - and usually Identifies the most common keyboards in only a few key presses.
- eitland 6y agoSame method as certain mainstream Linux distros has been using the last few years? Or has Mac been doing this for even longer (I cannot remember how it worked back in 2012, the last time I used Mac.)
- Zekio 6y agoIf it is in the browser it is probably just displaying using you local date time format
- oauea 6y agoHa, no.
- deleted 6y ago[deleted]
- jacobolus 6y agoI have taken to writing 11 March 2021 or similar whenever possible. But sure, 2021-03-11 is also fine, when trying to save something machine readable. The US conventions are indeed horrendous.
- Mordisquitos 6y agoAnother great thing about 2021-03-11 is that, even putting aside its technical advantages, it is (probably) intuitively understandable to any literate person even if they have never seen it before and, most importantly, it is almost immune from confusion because (hopefully) nobody is insane enough to expect YYYY-DD-MM. YYYY-MM-DD both satisfies the American intuitive expectation of month coming before day, and the Worldwide expectation of time units being displayed in a logical order.
- jacobolus 6y agoI have seen non-Americans write YYYY/DD/MM before. Hyphens are key here.
- happymellon 6y agoThat is horrifying. I am glad I have never met these people.
- PeterisP 6y agoyyyy.dd.mm. (but not with hyphens!) are commonly used for all the languages where their grammar and word order means that the spoken way to say dates is like "twothousandtwentieth year's first march".
- happymellon 6y agoeye_twitch.gif
- silvestrov 6y ago
- lloeki 6y agoThe best part is when someone tried to make it work for the other 96% of the world but failed for 2% of the dates (probably because the other locales got less testing, again very US centric), so one ends up with mixed US/EU dates (the latter often also uses / as a separator, as . is only used in some EU countries). It's so much fun trying to retrospectively correlate fatal incident data and failing to make sense of anything because some dates are inconsistent. Of course those dates are all the ambiguous kind, otherwise it wouldn't be -that- hilarious /s.
- inetknght 6y ago> It's the most obnoxiously American attitude imaginable to ignore this issue because it doesn't affect them... As an American I can fully confirm that 3/11/2011 is obnoxiously ambiguous. It affects us. But most Americans (particularly outside of science / engineering fields) are too thick-headed to recognize the problem or think about ways to improve it. So I do what I can. I don't even ask what time format something belongs in. I just write ISO8601 by default. If someone complains then I point them to the international standard and ask whether we want to be an internationally standards-compliant company. One manager said that our customers aren't international. It was a reasoned argument and I like having customers. But all others drop the argument at "international company" and "standards-compliant"
- Mauricebranagh 6y agoPoint them at the fiasco where NASA mixed up Imperia and Metric. And also ask but why are we not targeting international customers.
- inetknght 6y agoI have indeed done the former when discussing why I use meters instead of feet. The latter was an ice rink whose customers are very physically local. Local teams do compete internationally but the ice rink itself isn't an international org.
- fatnoah 6y ago>So I do what I can. I don't even ask what time format something belongs in. I just write ISO8601 by default. If someone complains then I point them to the international standard and ask whether we want to be an internationally standards-compliant company. This is my approach as well. I've never gotten a complaint about it, which proves to me that the format is understandable AND unambiguous.
- amelius 6y agoHow can you take an international standard seriously when it is based on the number of years since some prophet of some specific religion was thought to be born?
- FeepingCreature 6y agoAnother example of obnoxious American attitude: the TZ variable in POSIX. TZ=UTC+8. Is your system now set to the timezone UTC+8? No, it's set to UTC-8. Why? I don't know, but I suspect the people who developed this convention, who lived in the US, just didn't want to type a minus.
- jacobolus 6y agoThe TZ format counts how many hours behind UTC you are (how many hours should you add to get UTC time). The ISO format counts how many hours ahead of UTC you are. Neither choice is inherently correct, but the discrepancy is pretty annoying. Use https://en.wikipedia.org/wiki/Tz_database https://en.wikipedia.org/wiki/Tz_database names instead.
- dfee 6y ago> It's the most obnoxiously American attitude imaginable to ignore this issue because it doesn't affect them... only the other 96% of the planet. I’m not going to comment on the author, though I will acknowledge the abrasive, unhealthy attitude. Anyway, no. I don’t think there’s a clear “American” standard. Maybe there once was, but I’d just see a pile of numbers these days. It’s hostile to the consumer as it inherently leaves some uncertainty of how it should be consumed. I will say, and maybe this is American - but I don’t think it is - that I often see dates formatted unambiguously as, e.g. March 11, 2021.
- nicoburns 6y agoIt is American. In the UK, we'd write 11th March 2021. But I don't mind too much when it's non-ambiguous like this.
- bombcar 6y agoIs that also how you’d say it? If verbally asked what tomorrow is would you say “twenty seven February” or “twenty seventh February” or “twenty seventh of February”? Americans normally would say “February twenty seventh”.
- wankeler 6y agoYes. The 27th, or the 27th of February. To us, US English seems to skip a lot of the small joining words of various flavours.
- readflaggedcomm 6y agoIt's more obnoxious to be lectured by people who think "June 3rd, 2021" isn't shorthand for "AD 2021 June 3rd", which is proper logical and sorting order.
- arrow7000 6y agoYou're saying that 06-03-2021 is shorthand for 2021-06-03 and are confused why people don't get that?
- jlelse 6y agoThis reminds me about Americentrism: https://jlelse.blog/thoughts/2021/02/americentrism https://jlelse.blog/thoughts/2021/02/americentrism America first!
- TeMPOraL 6y agoYup. I hate // AM/PM formats with a passion. Doesn't help that I work with UK teams now, and their "natural" date format is 3/11/2021, with meaning of 3 and 11 reversed to what they'd mean for Americans... sigh. ISO 8601 everything. I'm religious about it. I write it in messages, on government forms, anything that doesn't force me to use a different format. On a bit of my insistence, we use ISO 8601 notation for all dates at home. I think the benefit is quite obvious once one starts using it.
- andy_ppp 6y agoFormat the date on the frontend using date.toLocaleDateString() and let the browsers locale do the work for you (assuming you’re in JS and on the web).
- rhn_mk1 6y ago> Date().toLocaleDateString() > Uncaught TypeError: Date().toLocaleDateString is not a function That doesn't seem like a standard API call.
- bmn__ 6y agoIt is standardised and widely implemented. https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleDateString#specifications https://developer.mozilla.org/docs/Web/JavaScript/Reference/... Your code has a bug, missing constructor.
- teh_klev 6y agoLooks like an instance method, rather than a static.
- TeMPOraL 6y agoNo. The computer cannot magically detect the preferences of an actual user. This is a kind of "90% solution" that excludes people whose locale setting doesn't match their preferences, which is arguably quite common. Reasons include buying your OS/computer from abroad, or one that was imported and resold, getting a work machine set up for a different country, not knowing how to fix locale up yourself, traveling (localizing websites based on user's location is idiotic, but it keeps happening).... What developers also suck at, in practice, is data-typing their output properly. If I see 5/2/11 on a US site while using my work laptop, I can't be sure whether it's the US notation written by the author, or date localized by my browser for UK format, which has the day and month reversed. I can't tell if the date is localized or not, or how it was generated. Just say no to all that complexity, and use ISO 8601 everywhere. My controversial view here is: in this industry, we're still in a privileged position to force the entire world to standardize on the important things, like dates and times. So let's do so, and get everyone on board with an international standard, instead of just unwittingly pushing the USA defaults. We are pushing things, that comes with "software eating the world". So let's push things that make sense.
- knorker 6y agoSure you can tell. You just hire an investigator to find out who wrote the memo, and find where in the world they grew up, in what culture. If the answer comes back very US, then it's middle endian US format. Else it's DMY. Note that the article is wrong to just say "dd.mm.yy" is used in "Europe". Some countries use yyyy-mm-dd and others dd/mm/yy. The US format is the only one that's retarded, though.
- lostlogin 6y ago> The US format is the only one that's retarded, though. I wonder how it started? A skim of the internets hasn’t enlightened me.
- bombcar 6y agoIt’s a representation of how us Americans talk - we rarely say 26th of February and instead say February 26 - and if necessary tack on the year. It feels exceptionally awkward to say 26 February, thought saying “twenty twenty one February 26” sounds very strange, too. But people are very good at verbally saying different than is written.
- knorker 6y agoSo write YYYY-MM-DD! But also, the most sacret of all days has been honored by the one day of the year "said properly" fourth of july!
- lostlogin 6y agoChanging formats is just asking for a large event on 9 November.
- frn123 6y agoNo native speaker but isn't 4th of July more common than July 4th?
- 6y ago
- yread 6y agoM/D/Y is a bit like the German way of reading numbers. 328 become three hundred, eight and twenty. Terrible
- slazaro 6y agoHow about french? 99 is four twenties nineteen, 79 is sixty nineteen. Languages are fun and fascinating.
- shdon 6y agoAnd since the French say ten nine instead of nineteen, it becomes four twenties ten nine.
- rswail 6y agoBut nineteen is just "nine and ten" with the "and" removed. English has a word for twenty and its used in the French way "Four score and seven years" is "quatre-vingts et sept".
- smcl 6y agoI think your response to these language quirks can vary depending on your familiarity with the language: - to an outsider, learning that a concept exists: “that is an interesting thing” - to a beginner, trying to construct the right form or to detect it in quickly spoken speech: “this is annoying and I hate it” - to an intermediate speaker and beyond: “eh it’s maybe weird but whatever” I used to hate noun declension in Czech as a beginner (7 cases x plural/singular = 14 forms a noun can take[0]) because it’s intimidating and unintuitive for an English speaker, but now I’m at the “meh” stage. [0] - then consider that there are 3 genders, and each gender has a handful of “models” (patterns for declining words that look a certain way), and also a bunch of exceptions. Not the hardest thing in the world, for sure. But it’s definitely a bit of a pain
- bombcar 6y agoI’ve always thought it’s interesting how the languages like that (most of the Romance languages have declensions and such) add error detection and even correction - you can figure out parts that are missing or got changed by the lack of agreement between the various forms. You may not be able to correct it from the Information available but you’ll know something went wrong.
- GordonS 6y agoYou can change the display format, but I really wish M/D/Y wasn't the default - it's just too ambiguous.
- Gys 6y agoIt is exaclty this attitude what makes the datetime format in Golang extremely difficult to use. I always have to double check my formatting. I like the basic idea very much, but its logic only works for 'local' Americans. The reference time used in the layouts is the specific time: Mon Jan 2 15:04:05 MST 2006 which is Unix time 1136239445. Since MST is GMT-0700, the reference time can be thought of as 01/02 03:04:05PM '06 -0700` Golang was not meant to become a big international language from the start? Just a fun internal Google project ;-)
- HenryBemis 6y agoOn presentations for projects I tend to add a couple of 'fun' slides. When said projects involve people in the USA, I (almost always) include the XKCD ISO 8601 cartoon: https://xkcd.com/1179/ https://xkcd.com/1179/ It is one of my favourites (the "8601", the "Security", and the "Bobby Tables")
- samwhiteUK 6y agoThis is mentioned in the article....
- dingaling 6y ago> only the other 96% of the planet Ahem, ISO8601 fails for Taiwan and Japan...
- account42 6y agoHow does it "fail"? Taiwan has different year numbers but they are sufficiently offset to avoid disambiguity and IME people can read normal years just fine. Anyway, the year-month-day order seems to be the same.
- heipei 6y agoI don't know, I'm German and deal with US folks a lot, for me it's like this: Date written with slashes or dashes (3/11/2021 or 3-11-2021) implies US-based month/day/year. Date written with dashes and the year first and zero-padding (2021-03-11) implies year-month-day, aka ISO8601. Date written with dots and without padding (11.3.2021) implies my native format, day.month.year.
- edoceo 6y agoIsn't the point of ISO to eliminate that guess/search process and replace with 100% accuracy on read?
- rodelrod 6y agobut then you get an email from an American living in Paris and it's 11/3/2021 with dashes and God knows what he meant.
- Macha 6y agoUK/Ireland are pretty interchangeable about the seperators, but I'd guess D/M/Y has a strong lead over second place d/m/y, while d.m.y is trailing in last.
- exporectomy 6y agoIt doesn't help at all if they try to localize it because then it's just 11/3/2021 which is equally confusing and you have no idea if they're using your local format or theirs. Any what's your local format? The country you're in or the country you were in when you signed up for the service or the country your VPN server is in? Internet services really need to stop using these stupid mistake-inducing, time wasting date formats. People might have a sense of unfamiliarity seeing ISO8601 format but they can still understand it. I use ISO8601 dates everywhere possible. Paper forms in the real world where people look at me strangely, invoices, file names which is really handy for sorting, my personal todo lists, everything.
- notatoad 6y agoThe AWS console is absolutely terrible for this, not just because it disobeys my preferred date format but because it's not even internally consistent. sometimes it converts timestamps to my local timezone, sometimes it displays them in UTC, sometimes it displays them in ISO8601 format, sometimes it displays them in US format.