3 ms·
The log/slog package is huge. I'm super happy to see them start-again to express opinions and solve more problem with just the standard library; and I hope to s
by 015a 3y ago
The log/slog package is huge. I'm super happy to see them start-again to express opinions and solve more problem with just the standard library; and I hope to see more of it. This was Go's Thing at 1.0; you could build a production ready, large scale HTTP service with nothing but the standard library; and, probably, a structured logging package like Zap. Now; looks like we may not need it!
If anyone on the Go team is reading this; thanks! And, as hacker news must always be the armchair commentator, if I may ask for an addition in go 1.22: encoding/yaml. Build it in. Go and YAML are the languages of devops, and I've written so many scripts with JSON as a configuration file only because Go has a JSON parser built-in, but not YAML.
- liggitt 3y ago> if I may ask for an addition in go 1.22: encoding/yaml FYI, encoding/yaml was recently requested, and was declined in https://github.com/golang/go/issues/61023#issuecomment-1610605569 https://github.com/golang/go/issues/61023#issuecomment-16106..., for reasons I largely agree with. (I work for Google but not on Go)
- masklinn 3y ago> I've written so many scripts with JSON as a configuration file only because Go has a JSON parser built-in, but not YAML. Sounds like a feature. Less Yaml in the world is a good thing.