🇺🇦 Go for two :)
СтатистикаTelegram channel about tricks and engineering practices in the Go programming language over a cup of coffee ☕️. author: @a_soldatenko personal blog: https://asoldatenko.org #golang #go #kubernetes #debugging
- Последний пост
- 21 февр.
- Последнее чтение
- 15:13
- Постов за неделю
- 0
- Всего постов
- 20
- Тип
- открытый
- Язык
- английский
- Категория
- Технологии (по похожим)
- В каталоге с
- 13 авг.
- 1/24сутки в ленте
- —
- 1/48двое суток
- —
- 1/72трое суток
- —
Оценка по просмотрам недавних постов: пост набирает почти всё за первые сутки.
Посты
„Interesting times“ What should we do with CLs generated by AI? https://groups.google.com/g/golang-dev/c/4Li4Ovd_ehE/m/UU87HnL5DgAJ?pli=1
https://www.reddit.com/r/RedditEng/comments/1mbqto6/modernizing_reddits_comment_backend_infrastructure/
Hey k8s/containers users! Go 1.25 not yet released but will be container aware of GOMAXPROCS https://tip.golang.org/doc/go1.25#container-aware-gomaxprocs
Nice satire article https://www.justfuckingcode.com/ 🙂 Kinda true in many directions 🙂
Classics https://status.redhat.com/ > Quay.io has been moved to read-only mode while we work to implement a fix. During this time Pulls will continue to work, however, Pushes will be disabled until a fix is implemented. There is currently no timeline for Push restoration. > The issue has been identified. A primary key in the database has reached maximum value. We are currently working on validating a fix.
Interesting approach by Russ for finding bugs by diff code coverage profiles between faing and success exectuon: https://research.swtch.com/diffcover
"Programming Is Like S*x: One mistake and you have to support it for the rest of your life." — Michael Sinz 😭😭😭
FYI: https://semgrep.dev/blog/2025/popular-github-action-tj-actionschanged-files-is-compromised/ https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised
Channel name was changed to «🇺🇦 Go for two :)»
After releasing go1.24, we can manage tools as dependencies! Here is very good step by step article about how to do it https://www.alexedwards.net/blog/how-to-manage-tool-dependencies-in-go-1.24-plus Also it includes example how to add tools to seperate go.mod file (TIL!)
it's really sad :( https://github.com/golangci/golangci-lint/issues/5300#issuecomment-2615552467
TIL: strings.Split returns [""] if s does not contain sep and sep is not empty 😅 package main import ( "fmt" "strings" ) func main() { fmt.Printf("%q\n", strings.Split("", ",")) } Split returns a slice of length 1 whose only element is s: [""]
Dont forget to share your feedback about developing with Go ✍️ https://go.dev/blog/survey2024-h2
Providing context to cancellations in Go 1.20 with the new context WithCause API https://josephwoodward.co.uk/2023/01/context-cancellation-cause-with-cancel-cause and proposal https://github.com/golang/go/issues/51365
видео или голосовое, без подписи
Some pitfalls about generating Kubernetes Custom Resources with `controller-gen` over the years, and how to do more rigid validation and defaulting with it: https://ahmet.im/blog/crd-generation-pitfalls/
Old but still worth to read about why one shouldn;t defer Close() on writable files: https://www.joeshaw.org/dont-defer-close-on-writable-files/
_4chan := make(chan chan chan chan int) 😅😅😅 https://www.dolthub.com/blog/2024-08-23-the-4-chan-go-programmer/
видео или голосовое, без подписи
For all GO haters :) https://juli1.substack.com/p/why-i-fell-in-love-with-go Nice quote and summary: >Technologies like JavaScript or Go are like a good burger: it’s an option that the majority understand and choose regularly. It may not be the most elegant option, but it does the job and allows us to focus on problems that matter.