HN Hall of Fame Weekly email

Why Go Is Not Good

Screenshot of yager.io captured 2026-07-20
Page preview · captured 2026-07-20

Resurfaced independently across 4 calendar years, with breakout response in 2 of them.

submissions
5
submitters
5
observed span
2014–2021
peak thread · 453 comments
438 pts
latest 20+ return · 2015-12-09
413 pts

Submission timeline

2007–2026

One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.

First comments on top threads

HN comment order

There's something very seductive about languages like Rust or Scala or Haskell or even C++. These languages whisper in our ears "you are brilliant and here's a blank canvas where you can design the most perfect abstraction the world has ever seen." But, for systems programming, abstractions suck. They always, always have a cost. When abstractions break, you not only have to deal with a broken system but the broken abstraction itself too. (Anyone who has ever seen a gcc…

mustpax·438-point thread·

https://news.ycombinator.com/item?id=7962345 << 527 days ago, 356 comments

Previous discussion: https://news.ycombinator.com/item?id=7962345

Dewie·15-point thread·

The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.

Breakout years
2

100+ points or 50+ comments

Total points
870

reference only — not used in Hall rules or ranking

Total comments
811

reference only — not used in Hall rules or ranking

Every submission

DateTitle as submittedByPointsComments
2014-06-29Why Go Is Not GoodFirst breakout · Best threadpohl438356
2014-12-02Why Go Is Not Goodsgt152
2015-12-09Why Go Is Not Good (2014)Latest 20+ point returnkushti413453
2017-10-27Why Go Is Not Goodmax056320
2021-03-09Why Go is not good (2014)tosh20