It was something not in the library because it wasn't in their sphere of consideration. When that expanded, due to feedback from the outside world, they responded in an impressive way.
And that's just an example that was intended to illustrative.
You'll just have to take my word for it that my experience of the Go ecosystem, tools, and standard library has been more solid than the various other things I've used over the years (python, C# + unity, c++, fucking maven, boost...).
If I'm missing out on something even better, let me know. ;-)
> This was a hack necessary because the design of the library wasn't fully thought out.
Easy to say 'not fully thought out'. It took Java from version 1.2 to 1.8 to fix its date/time library.
Re:The State of Go
by AdieuToLogic on Monday February 06, 2017 @12:12AM
(#13576676)
It took Java from version 1.2 to 1.8 to fix
its date/time library.
0 - http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22joda-time...
1 - https://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt
Seems to be some cognitive dissonance (in the modern erroneous sense of the word) going on. This was a hack necessary because the design of the library wasn't fully thought out. Imagining the world would one day become Google is not thinking things out.