News for hackers. Stuff that matters.
Re:New in Go 1.20: wrapping multiple errors by masklinn on Sunday December 11, 2022 @09:01AM (#33943231)
> What I claim that Go's approach is far superior and easier to remember and use. [...] I mean, I get the attachment part, but I believe that more efficient approaches should get recognition, not punishement.

The Go approach is barely "more efficient" if your only consideration is exclusively US-centric, it's outright hell everywhere else, because US date formats make even less sense than their units. Go's datetime format is gimmicky, gimpy (it's missing a good fifth of the TR35 fields, to say nothing of the field formats), inextensible, and localisation-hostiles.

It's also telling that while Go made up this nonsense with date formats, they retained the significantly worse and more error prone printf formats for, well, printf, in case mixing the two might have been an option (as it is in python for instance).

Re:New in Go 1.20: wrapping multiple errors by divan on Sunday December 11, 2022 @09:08AM (#33943302)
> is exclusively US-centric

It's literally not a problem at all. It's just one bit of information to remember in your head (I explained in a sibling comment how common US-style date in software, so for anyone who used computer longer than their last iPhone, it's just one bit of information - either date in US style or not). But with Go formatting it's even simpler - you literally never think about it.

You just remember that it's "January 2nd" and that's it. I'm so surprised that people trying to present it as a huge problem, let alone "insane" or "bizzare".

Re:New in Go 1.20: wrapping multiple errors by masklinn on Sunday December 11, 2022 @09:14AM (#33943357)
> It's literally not a problem at all. It's just one bit of information to remember in your head

Your assertions do not make that a reality.

> But with Go formatting it's even simpler - you literally never think about it.

True, because you quickly learn to use something else.

Re:New in Go 1.20: wrapping multiple errors by divan on Sunday December 11, 2022 @09:22AM (#33943446)
> Your assertions do not make that a reality

What reality? I write Go almost daily for 9 years and was running Golang meetups in two countries for years. I think I have pretty good grasp of what actual problem real people have with dates in Go. Order of day-month in mnemonic ("Jan 2nd" vs "Feb 1st") is literally not a problem. This problem exists only in HN comments of people used to other approaches.

Re:New in Go 1.20: wrapping multiple errors by fsociety on Sunday December 11, 2022 @11:13AM (#33944415)
That’s cool. I constantly get tripped up with day/month ordering. Maybe I am dumb, but it is a silly design to defend in my opinion.
Re:New in Go 1.20: wrapping multiple errors by divan on Sunday December 11, 2022 @03:59PM (#33947432)
Can you elaborate in details how exactly you tripped by this?

Like, when you need to present current date so it looks like "11 December, 2022" - where your issue starts with Go's approach? Can you walk me through your thought process here? I'm genuinly curious.

Re:New in Go 1.20: wrapping multiple errors by fcarraldo on Sunday December 11, 2022 @11:55AM (#33944871)
> Order of day-month in mnemonic ("Jan 2nd" vs "Feb 1st") is literally not a problem

I mean, you literally got it wrong in this comment, so maybe it’s worth considering whether such a simple mistake might be hard to catch and thus cause real production issues?

Re:New in Go 1.20: wrapping multiple errors by Smaug123 on Sunday December 11, 2022 @01:25PM (#33945824)
(The GP was using the US convention to refer to the two dates 01/02 and 02/01, not trying to use two conventions to refer to a different date each.)
Re:New in Go 1.20: wrapping multiple errors by fcarraldo on Sunday December 11, 2022 @01:28PM (#33945848)
Ah, I see. Apologies to GP, but I believe the point is still reinforced - the biggest enemy of an engineer when it comes to dates is ambiguity.