Should Libraries Log or Propagate Errors?
Summary
This Lobsters post discusses whether libraries should log errors or propagate them, highlighting Go's slog design and the tension between silencing logs and enriching error context. It raises questions about observable behavior and where logging responsibility belongs in library code. A concise prompt for developers evaluating logging strategies in their Go projects.