Go standard library
Hacker ApprovedThe most recommended of 7 standard libraries
Recommended for a large, stable set of packages that let Go programs avoid third-party dependencies, though critics say parts are low quality.
Recommended for a large, stable set of packages that let Go programs avoid third-party dependencies, though critics say parts are low quality.
49 people gave an opinion
- recommend it
- 34
- criticize it
- 15
- approval share
- 69%
Recommended in 11 of 13 months
- November 2025: recommended
- December 2025: not recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 34 people recommend itNeeds 10 or more, met.
- 2.3 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 11 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Covers most needs without dependencies
“I use JSON because it's in the standard Go library, and most of the times, I rather use something weird than add a dependency.”
Comment from 2 Sep 2026 in “Why do so many tools have JSON config files?” “The only good thing about Go is that its standard library has enough coverage to do a reasonable number of things.”
Comment from 7 Mar 2026 in “UUID package coming to Go standard library” “It’s notorious for its comprehensiveness and how often you can write zero dependency applications as a result.”
Comment from 29 Jul 2026 in “OpenAI just open-sourced Codex Security” - Comment from 17 Jun 2026 in “Why stdx is not on crates.io”
- Comment from 24 Nov 2025 in “Shai-Hulud Returns: Over 300 NPM Packages Infected”
- Comment from 17 Jun 2026 in “Why stdx is not on crates.io”
- Comment from 21 Oct 2026 in “Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor”
- Comment from 25 May 2026 in “Migrating from Go to Rust”
Stable with few regressions
“I can't remember any regressions I experienced caused by code changes to the large stdlib at all in the last decade”
Comment from 7 Mar 2026 in “UUID package coming to Go standard library” “The stdlib has been very very stable since the first release”
Comment from 7 Mar 2026 in “UUID package coming to Go standard library” “the stdlib has been incredibly stable through its history”
Comment from 11 May 2026 in “Incident CVE-2024-Yikes” - Comment from 14 Oct 2026 in “Do Frameworks Matter Anymore?”
- Comment from 8 Mar 2026 in “UUID package coming to Go standard library”
Well maintained and heavily tested
“Golang seems to do a good job of keeping the standard library up to date and clean”
Comment from 1 Apr 2026 in “Axios Compromised on NPM – Malicious Versions Drop Remote Access Trojan” “the Go stdlib routines have been heavily, massively, tested in production by now”
Comment from 25 May 2026 in “Migrating from Go to Rust” “Go's well maintained stdlib just lets me get on with it.”
Comment from 14 Nov 2025 in “Zed is our office” Strong HTTP and encoding support
“Meanwhile in the real world, you've been able to reap the benefits of the solid encoding/json for over a decade now”
Comment from 20 Aug 2026 in “Malicious Rust Crate Arrayref Runs a Build-Time Payload” “it's got pretty much everything needed out of the box for web server development”
Comment from 20 Feb 2026 in “Farewell Rust” “Go’s stdlib has good support on both the server side and user space.”
Comment from 29 Apr 2026 in “FastCGI: 30 Years Old and Still the Better Protocol for Reverse Proxies” - Comment from 8 Jan 2026 in “An Honest Review of Go”
What people warn about
Each mark is one comment
Parts of library are low quality
“Go has a stronger standard library for certain use cases like basic CRUD web applications, but a lot of the Go standard library is also extremely low quality”
Comment from 20 Aug 2026 in “Malicious Rust Crate Arrayref Runs a Build-Time Payload” “golang's standard library both has fairly significant issues (json, no set type, very limited CLI flag parsing, UUID took until 1.28)”
Comment from 21 Aug 2026 in “Malicious Rust Crate Arrayref Runs a Build-Time Payload” “A huge portion of the Go standard library is extremely low quality as well.”
Comment from 17 Jun 2026 in “Why stdx is not on crates.io” - Comment from 20 Aug 2026 in “Malicious Rust Crate Arrayref Runs a Build-Time Payload”
Surprising zero-value and JSON behavior
“upstream adds new fields where the zero value is different from the previous behavior, causing users to silently drift away from the intended behavior”
Comment from 12 Aug 2026 in “Why Go Is an Ideal Language for AI-Assisted Software Engineering” “such that half the standard library explodes if you try to use it with zero values”
Comment from 11 Feb 2026 in “Parse, Don't Validate (2019)” “Stdlib json parsing is normalizing and lossy.”
Comment from 15 Aug 2026 in “Why Go Is an Ideal Language for AI-Assisted Software Engineering” Stubborn team and messy design
“don't try to fudge it the way that Go's standard library solution does”
Comment from 1 Oct 2026 in “Cops Can Bypass iPhone's Automatic Reboot to Get into Locked Phones” “The stubbornness of the Go standard library team knows no bounds.”
Comment from 26 Aug 2026 in “fork() Considered Harmful in macOS” “it's not like Go standard library is not a bit messy”
Comment from 8 Mar 2026 in “UUID package coming to Go standard library”
Other standard libraries people recommend
The four most recommended other standard libraries, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Go standard libraryThis page | 34 | 15 | 69% | 11 | — | Approved |
| C++ Standard Library | 15 | 23 | 39% | 8 | — | — |
| Python standard library | 13 | 7 | 65% | 8 | — | — |
| Rust standard library | 12 | 16 | 43% | 9 | — | — |
| Java standard library | 7 | 3 | 70% | 4 | — | — |
What people said
40 of the 57 comments that mention it, newest first. Each links to the original comment.
“I personally feel pretty good about depending on only the go stdlib”
“They'll be reliable and become faster over decades”
“don't try to fudge it the way that Go's standard library solution does”
“I use JSON because it's in the standard Go library, and most of the times, I rather use something weird than add a dependency.”
“The stubbornness of the Go standard library team knows no bounds.”
“golang's standard library both has fairly significant issues (json, no set type, very limited CLI flag parsing, UUID took until 1.28)”
“The code in those packages is so far from perfect it's absurd.”
“Meanwhile in the real world, you've been able to reap the benefits of the solid encoding/json for over a decade now”
“Go has a stronger standard library for certain use cases like basic CRUD web applications, but a lot of the Go standard library is also extremely low quality”
“Stdlib json parsing is normalizing and lossy.”
“upstream adds new fields where the zero value is different from the previous behavior, causing users to silently drift away from the intended behavior”
“It’s notorious for its comprehensiveness and how often you can write zero dependency applications as a result.”
“The only way to "clear the lines" in software is to eject them from the main codebase and into imported libraries with stable, well-documented, well-tested APIs”
“I agree the stdlib is great but the reality is production apps cannot be built using only it.”
“A huge portion of the Go standard library is extremely low quality as well.”
“for the majority of people writing stuff in Go, they can get 99% of the way there with the Go stdlib”
“Everything you need to do can be don in Go stdlib without opening yourself up to supply chain vulnerabilities”
“the real value add of golang's std lib is not that it is developed by the language authored”
“I appreciate Go for having so much useful stuff in the standard library.”
“it contains everything you need for 90% of cases”
“the Go stdlib routines have been heavily, massively, tested in production by now”
“the stdlib has been incredibly stable through its history”
“Go’s stdlib has good support on both the server side and user space.”
“The benefits are worth it judging by how ubiquitous Go, Java and .NET are.”
“I'd rather leverage billions of support paid by the likes of Google, Oracle and Microsoft to build libraries for me”
“Golang seems to do a good job of keeping the standard library up to date and clean”
“it’s actually pretty good and infinitely preferable to third party everything”
“it's not like Go standard library is not a bit messy”
“It's still just table stakes to not break stdlib.”
“I can't remember any regressions I experienced caused by code changes to the large stdlib at all in the last decade”
“The only good thing about Go is that its standard library has enough coverage to do a reasonable number of things.”
“The stdlib has been very very stable since the first release”
“it's got pretty much everything needed out of the box for web server development”
“such that half the standard library explodes if you try to use it with zero values”
“net/http as a full server framework, not just a request library”
“I can get more real work done with only the standard library than with any other language I've used”
“build a production-ready HTTPS (not just HTTP) server with just the standard library and a few lines of code”
“The Go standard library is a lot more comprehensive and usable than Node”
“Go's well maintained stdlib just lets me get on with it.”
“You can see how much organizational power this has by looking at the docs for Go's standard library.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.