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, 1:56:48 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

220 sources
I'm using Go's default HTTP client to make a few requests per second. I set a context timeout of a few seconds for each request. There are random 16 minute intervals where I only get the error `context deadline exceeded`. From what I found, Go's default client uses HTTP/2 by default. When a TCP connection stops working, it relies on the OS to decide when to time out the connection. Over HTTP/1.1, it closes the connection itself [1] on timeout and makes a new connection. In Linux, I guess the timeout for a TCP connection depends on `tcp_retries2` which defaults to 15 and corresponds to a time of ~15m40s [2]. This can be simulated by making a client and some requests and then blocking traffic with an `iptables` rule [3]. My solution for now is to use a client that only uses HTTP/1.1. [1] https://github.com/golang/go/issues/36026#issuecommen
Read the rest
In Golang disables Nagle's Algorithm by default
If you trace this all the way back it's been in the Go networking stack since the beginning with the simple commit message of "preliminary network - just Dial for now " [0] by Russ Cox himself. You can see the exact line in the 2008 our repository here [1]. As an aside it was interesting to chase the history of this line of code as it was made with a public SetNoDelay function, then with a direct system call, then back to an abstract call. Along the way it was also broken out into a platform specific library, then back into a general library and go other with a pass from gofmt, all over a "short" 14 years. 0 - https://github.com/golang/go/commit/e8a02230f215efb075cccd41... 1 - https://github.com/golang/go/blob/e8a02230f215efb075cccd4146...
In Golang disables Nagle's Algorithm by default
afaik, the `time` package [1] from the golang standard library has a brilliant support for (almost) everything about time, including timezone, leap year, months, duration. take timezone for example, time.Time.In [2] could be a good startpoint to learn how they do the conversion. [1]: https://github.com/golang/go/tree/master/src/time [2]: https://github.com/golang/go/blob/38cfb3be9d4868334562767771...
In Ask HN: Resources for learning/teaching time zone conversions and datetime math?
A wonderfully Go-like piece of magic: https://github.com/golang/go/blob/go1/src/pkg/image/gif/read... What's magic there seemed magical at the time because even Go's creators were only just coming to see the power of interfaces then. Now, having a decompressor read from a block reader, which reads in turn from some other place, is not magical, it's just good practice. This is from Go 1. Unfortunately, that file accumulated tons of other ugliness over time, as it dealt with the real world. I was one of the people who had to make that line less magic. Sorry Rob.
In Ask HN: What's the most elegant piece of code you've seen?
This is incorrect on multiple levels: there is no organization that has "exclusive" control over Go, much less Rust. There's a company (Google) that made Go, but they have no control over the source code itself beyond the terms of the non-proprietary license they provide it under[1]. Even the things that Google does w/r/t Go are not even remotely controversial in the context of the definition of proprietary software, like CLAs. Linux has a CLA! Comparing this to Borland or Microsoft is bizarre: Microsoft and Borland actually do have proprietary C compilers that they do not make publicly available in source code form. Those compilers in turn have all kinds of non-standard, proprietary extensions. The one thing that sets C apart from Rust and Go is the presence of an official ISO standard. But this isn't material to the definition of "propr
Read the rest
ietary" in the open source world. And, well, that ISO standard is itself copyrighted. [1]: https://github.com/golang/go/blob/master/LICENSE Edit: You shouldn't delete and re-write your comments. Here's the original comment I responded to: > That's a dubious claim, and irrelevant besides. They are proprietary, in the standard meaning of the word, because a single private organization has exclusive control over each, but whatever word you choose to describe that is up to you. > Google owns Go in a way that has never been true of Microsoft (or Borland or GNU or Apple...) when it comes to C. Edit 2: For the edited comment: you're setting up a distinction that does not matter for programming languages that do not have formal specifications. There is no "interface" to distinguish against, and the claim that Rust (or Go, or Python, or any other language without an ISO spec) is tacitly reserving all rights to the design of the language itself is completely unsubstantiated.
In Ask HN: Learn C in 2023?
>"That is incorrect: DNS lookups happen in userspace, not the kernel." That's not even a nit, it's just plain wrong. While getaddrinfo is a library function it will invoke a torrent of system calls - socket, connect, sendto, recvmesg, open, close, fstat etc. Unless a host is found in a local cache or in a file specified in nsswitch.conf, it invariably involves sending and receiving packets over the network. These network round trips are all a part of the "the query" and you can't have those without system calls. The query is a query to a distributed database. >"For example, most programs written in Go (such as Kubernetes itself) use their own resolver instead of https://www.man7.org/linux/man-pages/man3/getaddrinfo.3.html (or its predecessor, https://www.man7.org/linux/man-pages/man3/gethostbyname.3.ht...). This can lead to "fun" issues w
Read the rest
here the behavior between resolvers diverges, such as https://github.com/golang/go/issues/15419." This is also not incorrect: "By default the pure Go resolver is used, because a blocked DNS request consumes only a goroutine, while a blocked C call consumes an operating system thread. When cgo is available, the cgo-based resolver is used instead under a variety of conditions: on systems that do not let programs make direct DNS requests (OS X) ..." [1]. There is also a litany of other conditions that will cause it to use getaddrinfo instead. So it's really OS dependent. Windows also used the libc resolver until Go 1.18. [1] https://pkg.go.dev/net
In The life of a DNS query in Kubernetes
Minor nit: in the diagram labeled "the flow of a DNS query in Kubernetes," it says a DNS query is a syscall. That is incorrect: DNS lookups happen in userspace, not the kernel. This is usually by calling a library function in libc, but sometimes not. For example, most programs written in Go (such as Kubernetes itself) use their own resolver instead of https://www.man7.org/linux/man-pages/man3/getaddrinfo.3.html (or its predecessor, https://www.man7.org/linux/man-pages/man3/gethostbyname.3.ht...). This can lead to "fun" issues where the behavior between resolvers diverges, such as https://github.com/golang/go/issues/15419.
In The life of a DNS query in Kubernetes

Showing the 15 most recent of 220 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.