Channel

Go

@golang

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

19,290subscribers

+139 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID	-1001003436297
Type	Channel
Username	@golang
Description	// admin @denniselite // Denis Podlesnykh, a Golang Engineer go func() { channel <- news }() news := <-channel fmt.Sprintf("%s", news)
Created	Between 1 September 2015 and 31 December 2015— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	6 August 2026
Last confirmed live	17 August 2026
Measurements held	12
Confirmed unchanged	1 time, most recently 17 August 2026
On Telegram	t.me/golang

Growth

12 measurements spanning 11 days, net +139. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 19,130–19,311 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
17 Aug 2026, 18:05	19,290	+2
16 Aug 2026, 13:55	19,288	+5
14 Aug 2026, 19:16	19,283	+7
13 Aug 2026, 09:57	19,276	-2
12 Aug 2026, 13:14	19,278	+16
11 Aug 2026, 15:03	19,262	+19
10 Aug 2026, 17:37	19,243	+16
9 Aug 2026, 19:03	19,227	+23
8 Aug 2026, 20:11	19,204	+38
7 Aug 2026, 17:24	19,166	+15
6 Aug 2026, 16:47	19,151	no change
6 Aug 2026, 15:00	19,151	first reading

Engagement

20 posts held, back to 30 November 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 25 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 20 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos: 15
Links: 145

Lifetime counters from Telegram’s own channel header, read 18 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

3,874 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 32.7% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
❤	1,265	32.7%
👍	1,032	26.6%
🔥	601	15.5%
👎	257	6.63%
👏	241	6.22%
🤔	199	5.14%
🤯	169	4.36%
💩	110	2.84%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3,874reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 30 November 2023 to 20 March 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

20 Mar 2026, 16:16 UTC≈31,200 views246 reactionsread 18 August 2026

If you’re working with Go and care about performance, then check out the https://goperf.dev/ Here you can find not theoretical, but practical patterns applicable to memory issues, concurrency, and overall, real bottlenecks you hit in production. The guide has been recently updated with more depth (atomics, concurrency trade-offs, etc.), so worth revisiting even if you’ve seen it before. Solid reference to keep bo…

❤128👍47🔥26💩14👏12🤔9🤯8👎2

17 Jan 2026, 21:18 UTC≈21,100 views177 reactionsread 18 August 2026

Photo

Are Atomic Operations Faster and Better Than a Mutex? It Depends From the author: "Recently, while reviewing a pull request, a discussion arose about using sync/atomic versus sync.RWMutex. It’s a question that comes up often when writing concurrent Go code, so I thought it would make a great post" https://madflojo.dev/posts/are-atomic-operations-faster-than-a-mutex/

❤67👍30👏21🤔21💩18🔥17🤯2👎1

29 Nov 2025, 14:17 UTC≈24,200 views157 reactionsread 18 August 2026

Hello, folks, it's been a while. Re-sharing an interetsting recording from GopherCon 2025: Advancing Go Garbage Collection with Green Tea (youtube). TL;DR: Go 1.25 includes a new experimental garbage collector called Green Tea, available by setting GOEXPERIMENT=greenteagc at build time. Many workloads spend around 10% less time in the garbage collector, but some workloads see a reduction of up to 40%! There is an a…

👍60❤38👏16🔥13🤯12👎11🤔4💩3

18 Aug 2025, 13:09 UTC≈28,500 views181 reactionsread 18 August 2026

Be Careful with Go Struct Embedding Embedding structs can quietly mask deeper-nested fields: a duplicate field name isn’t ambiguous unless it appears at the same ‘depth’, meaning your program may choose an unintended value. https://mattjhall.co.uk/posts/be-careful-with-go-struct-embedding.html

👍89🔥23🤔19👎17❤14👏10💩7🤯2

31 May 2025, 10:23 UTC≈37,000 views186 reactionsread 18 August 2026

What's new in Go: Google I/O presentation https://www.youtube.com/watch?v=kj80m-umOxs&ab_channel=GoogleforDevelopers

❤82👍46💩24👎14🔥9👏6🤔3🤯2

9 Feb 2025, 14:13 UTC≈40,800 views284 reactionsread 18 August 2026

Go 1.24: A Major Improvement for Tooling: go tools 🛠 Hello, folks! The upcoming Go 1.24 (supposed to be coming this month, Feb 2025) introduces a new go tool command, aiming to significantly improve the way project-specific tools are managed. This update eliminates the need for the tools.go workaround, reduces dependency bloat, and improves performance through caching. So, - No more tools.go hacks - Faster execution…

👍128❤64🔥35👏18🤔14👎13🤯12

24 Dec 2024, 16:13 UTC≈34,100 views590 reactionsread 18 August 2026

Hello, dear community! I wish you Merry Christmas 🎄 Happy New Year 🎊 and great winter holidays ahead!☃️ ❄️ See you in 2025 👋

❤397👍85🔥54💩17👏15🤔15👎4🤯3

13 Dec 2024, 15:08 UTC≈37,500 views219 reactionsread 18 August 2026

Coming in Go 1.24: testing/synctest experiment for time and concurrency testing Testing code that involves time or concurrency can be a struggle. It often leads to hard-to-debug flakes in CI or long-running tests. Go 1.24 is scheduled to be released in February and the release freeze has begun. It’s set to include an experimental testing/synctest package designed to make testing code that involves time or concurre…

❤95👍45🔥26🤯16👏15🤔12💩9👎1

21 Oct 2024, 06:53 UTC≈39,400 views201 reactionsread 18 August 2026

Go Blueprint: A Quick Way to Start Go Projects ⚒ The tool helps you setting up new Go projects fast, with ready-made templates and all the basic setup done for you. While I’m not really into using tools like this, some might find it useful to save time and focus on development. From the authors: "Powerful CLI tool designed to streamline the process of creating Go projects with a robust and standardized structure. …

🔥72👍48❤29👎22🤔14👏12🤯3💩1

14 Oct 2024, 03:14 UTC≈33,900 views135 reactionsread 18 August 2026

Go sync.Map: The Right Tool for the Right Job In Go, sync.Map offers a thread-safe alternative to traditional maps. While sync.Map can be highly effective in scenarios involving heavy concurrent access, it isn't always the best choice. In this article by VictoriaMetrics, you'll learn when to opt for sync.Map, how it differs from regular maps, and the performance trade-offs involved. https://victoriametrics.com/blog…

👍44❤33👎27🤔13👏6💩5🔥4🤯3

7 Sept 2024, 18:44 UTC≈35,600 views153 reactionsread 18 August 2026

The standard library of Go 1.23 now includes the new unique package. The purpose behind this package is to enable the canonicalization of comparable values. In other words, this package lets you deduplicate values so that they point to a single, canonical, unique copy, while efficiently managing the canonical copies under the hood. You might be familiar with this concept already, called “interning”. Let’s dive in to…

🔥73❤29👏25👍24👎2

15 Jul 2024, 20:56 UTC≈38,900 views164 reactionsread 18 August 2026

If you use Timer.Reset() in Go 1.22 or earlier, you may be doing it wrong. Even the book 100 Go Mistakes (which is usually right about Go nuances) got it wrong. Let's see what the problem might be and how to work around it. https://antonz.org/timer-reset/

🤯56👍46🔥16🤔14❤13👎11👏8

Showing the 12 most recent of 20 posts we hold for @golang. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 535,611 of 1,548,671entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Gopher Feed (Golang)
@GopherFeed · 2221 post

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

مجتمعات التيليجرام التقنية والسيبرانية
@TelegraamForITNerds · 2001 post

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 17 August 2026 — this entry's latest reading, not the date you are reading this.

“Go” (@golang), 19,290 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/golang.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.