Go Library
رفتن به کانال در Telegram
Go (Golang) Library Реклама: @ostinostin Контент: @mxssl
نمایش بیشتر
شبکه:4 361
مشترکین
+724 ساعت
+277 روز
+2430 روز
در حال بارگیری داده...
کانالهای مشابه
ابر برچسبها
اشارات ورودی و خروجی
---
---
---
---
---
---
جذب مشترکین
ژوئیه '26
ژوئیه '26
+54
در 3 کانالها
ژوئن '26
+45
در 1 کانالها
Get PRO
مه '26
+47
در 1 کانالها
Get PRO
آوریل '26
+59
در 0 کانالها
Get PRO
مارس '26
+60
در 0 کانالها
Get PRO
فوریه '26
+57
در 0 کانالها
Get PRO
ژانویه '26
+90
در 0 کانالها
Get PRO
دسامبر '25
+50
در 0 کانالها
Get PRO
نوامبر '25
+85
در 0 کانالها
Get PRO
اکتبر '25
+85
در 1 کانالها
Get PRO
سپتامبر '25
+62
در 1 کانالها
Get PRO
اوت '25
+48
در 1 کانالها
Get PRO
ژوئیه '25
+22
در 0 کانالها
Get PRO
ژوئن '25
+56
در 1 کانالها
Get PRO
مه '25
+60
در 1 کانالها
Get PRO
آوریل '25
+44
در 1 کانالها
Get PRO
مارس '25
+84
در 2 کانالها
Get PRO
فوریه '25
+56
در 0 کانالها
Get PRO
ژانویه '25
+103
در 1 کانالها
Get PRO
دسامبر '24
+58
در 1 کانالها
Get PRO
نوامبر '24
+88
در 1 کانالها
Get PRO
اکتبر '24
+111
در 0 کانالها
Get PRO
سپتامبر '24
+108
در 0 کانالها
Get PRO
اوت '24
+99
در 0 کانالها
Get PRO
ژوئیه '24
+196
در 0 کانالها
Get PRO
ژوئن '24
+73
در 0 کانالها
Get PRO
مه '24
+302
در 0 کانالها
Get PRO
آوریل '24
+248
در 1 کانالها
Get PRO
مارس '24
+71
در 0 کانالها
Get PRO
فوریه '24
+50
در 1 کانالها
Get PRO
ژانویه '24
+65
در 0 کانالها
Get PRO
دسامبر '23
+52
در 0 کانالها
Get PRO
نوامبر '23
+24
در 0 کانالها
Get PRO
اکتبر '23
+33
در 1 کانالها
Get PRO
سپتامبر '23
+32
در 0 کانالها
Get PRO
اوت '23
+33
در 0 کانالها
Get PRO
ژوئیه '23
+28
در 0 کانالها
Get PRO
ژوئن '23
+45
در 0 کانالها
Get PRO
مه '23
+62
در 0 کانالها
Get PRO
آوریل '23
+115
در 0 کانالها
Get PRO
مارس '23
+252
در 0 کانالها
Get PRO
فوریه '23
+48
در 0 کانالها
Get PRO
ژانویه '23
+66
در 0 کانالها
Get PRO
دسامبر '22
+17
در 0 کانالها
Get PRO
نوامبر '22
+41
در 0 کانالها
Get PRO
اکتبر '22
+34
در 0 کانالها
Get PRO
سپتامبر '22
+33
در 0 کانالها
Get PRO
اوت '22
+44
در 0 کانالها
Get PRO
ژوئیه '22
+33
در 0 کانالها
Get PRO
ژوئن '22
+77
در 0 کانالها
Get PRO
مه '22
+59
در 0 کانالها
Get PRO
آوریل '22
+168
در 0 کانالها
Get PRO
مارس '220
در 0 کانالها
Get PRO
فوریه '220
در 0 کانالها
Get PRO
ژانویه '22
+30
در 0 کانالها
Get PRO
دسامبر '21
+41
در 0 کانالها
Get PRO
نوامبر '21
+53
در 0 کانالها
Get PRO
اکتبر '21
+64
در 0 کانالها
Get PRO
سپتامبر '21
+57
در 0 کانالها
Get PRO
اوت '21
+45
در 0 کانالها
Get PRO
ژوئیه '21
+42
در 0 کانالها
Get PRO
ژوئن '21
+70
در 0 کانالها
Get PRO
مه '21
+41
در 0 کانالها
Get PRO
آوریل '21
+69
در 0 کانالها
Get PRO
مارس '21
+60
در 0 کانالها
Get PRO
فوریه '21
+80
در 0 کانالها
Get PRO
ژانویه '21
+72
در 0 کانالها
Get PRO
دسامبر '20
+2 443
در 0 کانالها
| تاریخ | رشد مشترکین | اشارات | کانالها | |
| 12 ژوئیه | +1 | |||
| 11 ژوئیه | +7 | |||
| 10 ژوئیه | +17 | |||
| 09 ژوئیه | +1 | |||
| 08 ژوئیه | +3 | |||
| 07 ژوئیه | +4 | |||
| 06 ژوئیه | +2 | |||
| 05 ژوئیه | +2 | |||
| 04 ژوئیه | +6 | |||
| 03 ژوئیه | +5 | |||
| 02 ژوئیه | +4 | |||
| 01 ژوئیه | +2 |
پستهای کانال
How much do amd64 microarchitecture levels help in Go?
Our 64-bit Intel and AMD processors have evolved over decades. When you compile a Go program for a 64-bit Intel or AMD processor, the compiler targets, by default, a nearly 20-year-old instruction set. The binary that comes out runs on essentially any x64 chip, but it also leaves on the table every instruction that was added since 2003.https://lemire.me/blog/2026/06/06/how-much-do-amd64-microarchitecture-levels-help-in-go
| 2 | Socket-Activation for a Go HTTP service. Part 1: On Linux with systemd.
How to make systemd run a Go HTTP service only when needed to save cpu/memory.
https://poweruser.blog/socket-activation-for-a-go-http-service-part-1-on-linux-with-systemd-0e530ed463a3 | 429 |
| 3 | nodecore
A fault-tolerant, API-agnostic RPC load balancer for blockchain APIs.
https://github.com/drpcorg/nodecore | 546 |
| 4 | I taught a bucket to speak git
What happens if I just point a git server at an object storage bucket?
Back when I was porting agent sandboxes to Go, I built everything on top of billy, a filesystem abstraction for Go. The whole trick of the project was teaching a Tigris bucket to act enough like a filesystem that a shell interpreter and its tools couldn’t tell the difference. Billy was the key layer that made the entire façade fall into place.
After I had gotten things working, I learned that I’m using billy way outside its normal usecase. It was originally made for go-git, a pure-Go implementation of git’s protocols and data formats. It doesn’t rely on the /usr/bin/git binary existing at all. Every method on billy’s filesystem interface exists purely because go-git needs it. This gave me a terrible idea: I already have a bucket that can quack like a filesystem and go-git’s native language is “filesystem”.
Can this Just Work™? Let's find out.
https://www.tigrisdata.com/blog/objgit | 552 |
| 5 | Don't run SQL migrations in tests: How I sped up the test suite by 2x
We have a giant test suite at work, mostly in Go. The test coverage is great, but it means that it's not that fast to run, and it only will get slower over time as new tests are added. Almost every test needs a pristine database. We are spending a ton of CPU time just applying again and again the same SQL migrations at the start of each test.
https://gaultier.github.io/blog/I_sped_up_the_test_suite_by_x2.html | 633 |
| 6 | Excelize v2.11.0: an important release with security fixes for XLSX reading, lower memory usage, and improvements to formulas, charts, and pivot tables. Includes breaking changes: Go 1.25+ is now required, and some chart/shape APIs were changed.
https://github.com/xuri/excelize/releases/tag/v2.11.0 | 669 |
| 7 | Channel iteration and goroutine leak
I ran into the classic “range over a channel” leak while working on a custom cron scheduler. I’ve debugged it on prod many times before, but writing one myself in a small piece of code reminded me how easy it is to write bugs like this even when you know about it.
https://rednafi.com/go/channel-iteration-goroutine-leak | 703 |
| 8 | Excessive nil pointer checks in Go
Let’s talk about nil pointer checks in Go. You want to prevent panics in production, but that doesn’t start with a deferred recover. It starts with defensive programming. Check your inputs, check your bounds, and check pointers for nil before dereferencing them.
I’ve started to see more nil checks in Go code. In the right place, they are necessary for writing safe code. In the wrong place, they are a sign that the code has stopped being clear about what can and cannot be nil. I have noticed this pattern more in generated code, but this symptom is not new and is not limited to AI.
When a nil check is cheap and prevents a panic, why not add it? Your reflex may be, let’s just be safe. But the check also tells the next reader something, and often the wrong thing.
https://konradreiche.com/blog/excessive-nil-pointer-checks-in-go | 774 |
| 9 | Shard your locks: benchmarking 6 Go cache designs
TL;DR: Shard your locks. A 256-way striped map (sharded) was the all-around winner — up to 8× faster than a single sync.Mutex at 8 cores — and it’s about 15 lines of code. sync.RWMutex, the reflexive fix for “reads are contended,” is a trap: it barely helps reads past two cores and is slower than a plain mutex for writes.
https://strebkov.dev/posts/shard-your-locks | 796 |
| 10 | router
Model router for agentic systems. Routes every prompt to the right model in <50ms. Cut costs 40-70% with just an endpoint change.
https://github.com/workweave/router | 832 |
| 11 | hasp
HASP is a local secret broker for coding agents.
Agents need credentials to run tests, call APIs, and deploy code. Copying those credentials into prompts, shell history, .env files, or repo-local notes makes the agent faster today and harder to trust tomorrow. HASP keeps secrets in a local encrypted vault and gives commands only the values they are allowed to use at runtime.
The core rule is:
Managed secret values must not enter agent context.
https://github.com/gethasp/hasp | 894 |
| 12 | gopls's Model Context Protocol (MCP) Server
Gopls includes an experimental built-in server for the Model Context Protocol (MCP), allowing it to expose a subset of its functionality to AI assistants in the form of MCP tools.
https://go.dev/gopls/features/mcp | 919 |
| 13 |  🔍 ТОП-5 ошибок на алгоритмической сессии
Привет, на связи Таня Коровкина из ШОРТКАТ. Ментор по алгоритмам и backend-разработчик
Каждый месяц тысячи разработчиков совершают одни и те же ошибки на алгоритмических интервью 🚩
И продолжают готовиться... не к тому.
6 июля(понедельник) в 19:00 (МСК) проведу вебинар и покажу, что на самом деле оценивает интервьюер и какие ошибки чаще всего приводят к отказу
• дам практические советы, которые можно использовать уже на следующем собеседовании
• расскажу про специфику российского BigTech
🤘 Это бесплатно. Эфир проходит в рамках менторской программы от ШОРТКАТ для разработчиков, которые хотят повысить свой грейд, ЗП и прокачать скиллы.
Переходи в нашего бота, чтобы получить ссылку на эфир → @shortcut_go_bot
Реклама.
О рекламодателе. | 953 |
| 14 | Building Agents in Go Without a Framework
A production agent is a long-running, concurrent, I/O-bound process that spends most of its time waiting on a model, a tool, or a human. That shape fits Go's runtime. This post explains why, surveys the Go framework options, and shows how to build an agent without one.
https://blog.getzep.com/agentic-development-in-go | 859 |
| 15 | MaxBytes Middleware in Go: The Same Trap, Again
Most of my API accepts small JSON payloads, so a strict global limit is a sane default. File uploads need a couple of orders of magnitude more. And the obvious solution – overriding the limit with another middleware on that route – fails in exactly the same way. Silently.
https://destel.dev/blog/max-bytes-middleware-in-go | 910 |
| 16 | Dependencies should be fetched directly from VCS
One aspect where I do feel Go is clearly better is dependency management; specifically the security aspect thereof. Go is not magically immune to malicious dependencies, but it is a lot more resistant to them chiefly because there is no "publish a package" step.
https://www.arp242.net/deps-vcs.html | 947 |
| 17 | How does struct{} take zero bytes in Go
While learning Go, I came across struct{}. First as a way to implement memory-efficient sets, since it takes zero bytes. Then again with goroutines, where it's the standard way to send a signal over a channel. What I didn't fully understand was: how does something that takes zero bytes actually work under the hood?
https://www.bud1m.com/blog/go-empty-struct | 1 073 |
| 18 | Finding Leaked Goroutines in Go 1.27
Go 1.27 is getting a goroutine leak detector in runtime/pprof. The proposal was accepted in April.
https://rednafi.com/shards/2026/06/go-goroutine-leak-profile | 1 128 |
| 19 | Understanding the Go Runtime: The Reflect Package
https://internals-for-interns.com/posts/go-runtime-reflect | 1 125 |
| 20 | kor
Kor is a tool to discover unused Kubernetes resources.
https://github.com/yonahd/kor | 1 276 |
