go101 VS errors

Go101: An in-depth guide that explores Go's internals, perfect for understanding the language at a deeper level.

How about this: https://go101.org/ might help :)

Go 101 books, which cover every corner of the language itself (syntax, semantics, compiler and runtime implementation) and make more detailed explanations than the official docs in several points. (Author here)

https://go101.org/ - read this.

Best is a subjective word, but all Go 101 books are up-to-date. They are updated frequently. (Author here)

Go 101 books (https://go101.org/). Always up-to-date. (Author here).

overall balance and flexibility: https://github.com/go101/go101/wiki/The-main-sell-point-of-G...

Can you explain why we should this over https://github.com/pkg/errors?

Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors

Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.

And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)

pkg/errors or stdlib errors - Error handling, but I wrote my own package for that tailored to my projects' needs. (FYI primalskill/errors but please don't use it as it's not production-ready yet and it will change a lot)

https://github.com/pkg/errors - errors with stack traces

The pkg.go.dev page lists 14k+ projects importing it, but the Github repository has been archived which would seem to discourage use. I'm also not a huge fan of the naming conflict with the stdlib errors package. The README notes it went into maintenance mode but it appears this, too, has passed.

The pkg/errors and xerrrors are not maintainted