Careful, do not use the url.URL #Go type in structures if you expect to encode them in JSON. For some incredibly stupid reason, it will be serialized as a JSON object and not as the expected string representation. Forces you to use strings everywhere. So much for type safety…
@galdor Go's own types in the standard library annoyingly lack RFC-compatible JSON Un/Marshallers (same goes for time.Time). The issue is discussed for years and it doesn't look like there will be any change until Go 2, if it all.
@louis The Go standard library feels like it was not designed as a set of components working together and more like a collection of heterogenous utilities.
As for Ruby and Python, it is a demonstration of why a standard library should be kept separate from the core language and be allowed to change version after version instead of having its mistakes set in stone.
Add comment