HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
golang
go
Go2014–2026
golang / go

go

The Go programming language

1,181Distinct people
1,944Mentions
14Explicit recommenders
139.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Go programming language

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

> To convert the Stream.Reader to an std.Io.Reader, we need to call its interface() method. To get a std.io.Writer from an Stream.Writer, we need the address of its &interface…

j1elo used a recommendation phrase. 14 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year1,944 dated mentions

Observed mentions: 2014-12-08 08:41:45 UTC to 2026-10-22 10:17:39 UTC.

0501001502002014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 16 mentions; 1 submissions, 15 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 80 mentions; 17 submissions, 63 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 135 mentions; 18 submissions, 117 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 164 mentions; 20 submissions, 144 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 174 mentions; 26 submissions, 148 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 196 mentions; 30 submissions, 166 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 159 mentions; 21 submissions, 138 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 184 mentions; 34 submissions, 150 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 220 mentions; 45 submissions, 175 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 221 mentions; 27 submissions, 194 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 163 mentions; 13 submissions, 150 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 167 mentions; 24 submissions, 143 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 65 mentions; 15 submissions, 50 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC16115
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC801763
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC13518117
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC16420144
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC17426148
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC19630166
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC15921138
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC18434150
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC22045175
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC22127194
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC16313150
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC16724143
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC651550

From the project README

An excerpt from the repository, fetched Nov 12, 2026.

Read the project’s introduction
The Go Programming Language Go is an open source programming language that makes it easy to build simple, reliable, and efficient software. Gopher image by Renee French, licensed under Creative Commons 4.0 Attribution license. Our canonical Git repository is located at https://go.googlesource.com/go. There is a mirror of the repository at https://github.com/golang/go. Unless otherwise noted, the Go source files are distributed under the BSD-style license found in the LICENSE file. Download and Install Binary Distributions Official binary distributions are available at https://go.dev/dl/. After downloading a binary release, visit https://go.dev/doc/install for installation instructions. Install From Source If a binary distribution is not available for your combination of operating system and architecture, visit https://go.dev/doc/install/source for source installation instructions. Contributing Go is the work of thousands of contributors. We appreciate your help! To contribute, please read the contribution guidelines at https://go.dev/doc/contribute. Note that the Go project uses the issue tracker for bug reports and proposals only. See https://go.dev/wiki/Questions for a list of places to ask questions about the Go language.
Read the full README on GitHub

What Hacker News says

163 sources
> so the error value is clearly visible in function signature and must at least be explicitly ignored by the caller Not exactly. There's nothing requiring you to handle errors. But Go doesn't let you have unused values in general. So in a transaction commit function, if you forget that it returns an error, Go will just let you ignore it. This is a big issue with treating errors as values. https://github.com/golang/go/issues/20803
In Idiomatic Errors in Clojure
> I'm not sure why it gets brought up other than language level FOMO. I think it gets brought up because people see places it would be helpful quite often. A lot of the Go code I've written has: switch x { case ....: case ....: default: panic(fmt.Sprintf("inexhaustive match, please update this switch statement for %v", x)) } Similarly, go supposedly has good error handling, but I constantly find myself writing: switch { case err == nil: case errors.Is(err, SomeErr): // handle SomeErr case errors.Is(err, OtherErr): // handle OtherErr case strings.Contains(err.Error(), "tls: unknown certificate authority")): // handle unexported go stdlib error, XXX fix after https://github.com/golang/go/issues/35234 default: panic(fmt.Sprintf("unhandled error type: %v: %T", err, err)
Read the rest
) } Like, for being a statically typed language, Go's error handling is really bad, and sum types is the thing that would let me internally at least make error handling feel good. I could have my own functions return up a non `error`-interface type, not implement the `error` interface intentionally to avoid the nil-typed-interface problem 'err' is otherwise prone to, and then I could actually know when I compiled my codebase that my error handling is good, and know what needs to be updated after adding new error paths.
In Good union types in Go would probably need types without a zero value
Go without concurrency is fully memory safe. However, once you start using goroutines there can be memory corruption and segfaults: https://github.com/golang/go/issues/37484. Note that these are not recoverable panics (such as "writing to a close channel"), but causes completely arbitrary behavior: runtime: pointer 0xc00379ac60 to unused region of span span.base()=0xc001794000 span.limit=0xc001795e00 span.state=1 fatal error: found bad pointer in Go heap (incorrect use of unsafe or cgo?) runtime: nelems=8 nalloc=5 previous allocCount=4 nfreed=65535 fatal error: sweep increased allocation count
In Weak pointers in Go: why they matter now
Glojure author here! Your analysis is spot-on :). I'll definitely take a look at clojure.core-test. As components mature, I focus on improving compatibility by porting tests from Clojure [0], but they often require modifications to accommodate differences in the host language. As you noted, there are still several fundamental features missing — most notably some core data structures. That said, the implementation is robust enough to support another non-trivial hobby project [1]. A bit more detail on some of your observations: > No JIT or AOT compilation (right now). I do plan to implement AOT compilation eventually. JIT, however, is more complex. Go's "plugin" standard library [2] could serve as a mechanism, but its support is limited and not without issues [3]. > it looks like the analysis could be largely a port of tools.analyzer Exactl
Read the rest
y! Another key implementation strategy has been the handling of clojure.core. Instead of reimplementing everything from scratch, the Clojure 1.11 core libraries are programmatically transformed to work with Go [4]. However, this approach has its downsides — many functions appear to be available but are non-functional because parts of their implementation haven't yet been adapted. And by the way, impressive progress on Jank! I've been following it closely and really admire the work you're doing. [0] https://github.com/clojure/clojure/tree/master/test/clojure/... [1] https://github.com/jfhamlin/muscrat [2] https://pkg.go.dev/plugin [3] https://github.com/golang/go/issues/19282 [4] https://github.com/glojurelang/glojure/tree/808165fdc7e65672...
In Glojure: Clojure interpreter hosted on Go, with extensible interop support
Go has much more significant stack allocation capabilities, most notably it has no problem allocating entire structs on the stack so doesn't need scalar replacement, which falls over if you breathe on it (https://pkolaczk.github.io/overhead-of-optional/). According to https://github.com/golang/go/discussions/70257#discussioncom... > the weak generational hypothesis does not hold up well with respect to heap-allocated memory in many real-world Go programs (think 60-70% young object mortality vs. the 95% typically expected)
In Mark–Scavenge: Waiting for Trash to Take Itself Out
> it might completely upend the generational hypothesis The generational hypothesis is about object lifetime, and that doesn't change. It does change the relevance of the generational hypothesis to garbage collection. > Surely someone's done some studies on this? The go team has, and that's why go doesn't have a generational GC. The complexity of adding generational support, especially in a mutation-based language (so needing memory barriers and the like) was found not to benefit when a significant fraction of the newborn objects don't even reach the youngen. See https://github.com/golang/go/discussions/70257#discussioncom... from the current discussion of adding opt-in ad-hoc support for memory regions.
In Mark–Scavenge: Waiting for Trash to Take Itself Out
tapirl·Nov 17, 2024Recommendation phrase
The difference between types.Implements and types.Satisfies is mainly caused by a history reason. It is just a tradeoff between keeping backward compatibility and theory perfection. It is pity that Go didn't support the "comparable" interface from the beginning. If it has been supported since Go 1.0, then this tradeoff can be avoided. There are more limitations in current Go custom generics, much of them could be removed when this proposal (https://github.com/golang/go/issues/70128) is done. I recommend people to read Go Generics 101 (https://go101.org/generics/101.html, author here) for a thoroughly understanding the status quo of Go custom generics.
In Constraints in Go

Showing the 15 most recent of 163 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.