Hacker GitHub

← All repos

golang/go

View on GitHub ↗ ★ 139,735 Go

The Go programming language

1,947 mentions on Hacker News by 1,181 people: 291 stories, 1,656 comments · first 2014-12-08 · latest 2026-10-22

Mentions per year 1,947 mentions · busiest year 2023 (221)
20082026
  1. This should be automatic these days (for the basic scenarios). https://github.com/golang/go/blob/a1a151496503cafa5e4c672e0e...
    comment by yencabulator · 2025-05-21 · in Understanding the Go Scheduler
  2. Relevant proposal to make GOMAXPROCS cgroup-aware: https://github.com/golang/go/issues/73193
    comment by xyzzy_plugh · 2025-05-21 · in Understanding the Go Scheduler
  3. …bump into conversations in the golang community in the same vein just don't bother to save them: https://github.com/golang/go/issues/29461
    comment by rester324 · 2025-05-20 · in Too Much Go Misdirection
  4. Go's source code (comment actually) says it all tbh: https://github.com/golang/go/blob/master/src/io/io.go#L55 (very much) tldr: anything that implements `Read(p []byte) (n int, err error)` - is a Reader.
    comment by konart · 2025-05-19 · in Too Much Go Misdirection
  5. I am once again begging for this to be implemented: https://github.com/golang/go/issues/4146
    comment by nulld3v · 2025-05-19 · in Too Much Go Misdirection
  6. ▲ 2
    Green Tea Garbage Collector
    story by typical182 · 2025-05-15 · 0 comments
  7. ▲ 2
    Proposal: Net/HTTP: Add CrossOriginForgeryHandler
    story by todsacerdoti · 2025-05-12 · 0 comments
  8. …think the "implementation quality" is a far bigger determinant in explaining the current gap. [1]: https://github.com/golang/go/issues/11646 [2]: https://github.com/matloob/regexp
  9. ▲ 85
    Proposal: Add bare metal support to Go
    story by rbanffy · 2025-05-07 · 20 comments
  10. ▲ 13
    Green Tea: an experimental, memory-aware garbage collector for Go
    story by pdubroy · 2025-05-05 · 0 comments
  11. ▲ 20
    Runtime: Green tea garbage collector (Go)
    story by raggi · 2025-05-03 · 0 comments
  12. ▲ 6
    Go 'green tea' garbage collector
    story by asb · 2025-05-02 · 0 comments
  13. …as you noted it's a cache miss for this which causes the long application launch delay. [1] https://github.com/golang/go/issues/42684 has a bit more info on this, I'm happy to see that even seasoned experts are confused about these things.
  14. …designers don't get it. The entire point is to reduce the amount of typing and visual noise. [1]: https://github.com/golang/go/issues/57616#issuecomment-14509... [2]: https://github.com/golang/go/issues/34174#issuecomment-14509... [3]:…
    comment by Mawr · 2025-04-12 · in PEP 750 – Template Strings
  15. …the aliased operations on the line(s) before, then reference the final values. E.G. Adapting https://github.com/golang/go/issues/34174 f := 123.45 fmt.Fprintln("value=%08.3f{f}") // value=0123.450 fmt.Fprintln("value=%08.3f", f) //…
    comment by mjevans · 2025-04-11 · in PEP 750 – Template Strings
  16. That issue has a link to another Issue with more discussion: https://github.com/golang/go/issues/57616 . But as is all too common in the go community, there seems to be a lot of confusion about what is proposed, and resistance to any…
    comment by thayne · 2025-04-11 · in PEP 750 – Template Strings
  17. …Go team would not even release an experimental feature unless they feel quite good about it. [1] https://github.com/golang/go/issues/57616
    comment by unscaled · 2025-04-11 · in PEP 750 – Template Strings
  18. …with Go (compared to other languages), they're loathe to add new features to the compiler[2]. [1] https://github.com/golang/go/issues/34174#issuecomment-14509... [2] https://github.com/golang/go/issues/34174#issuecomment-53013...
    comment by unscaled · 2025-04-11 · in PEP 750 – Template Strings
  19. …f-strings since 2016, and now t-strings. [1]: https://news.ycombinator.com/item?id=40737095 [2]: https://github.com/golang/go/issues/34174#issuecomment-14509...
    comment by Mawr · 2025-04-10 · in PEP 750 – Template Strings
  20. https://github.com/golang/go/blob/master/src/sync/pool.go#L2... The GC calls out to sync.Pool's cleanup.
    comment by andrewf · 2025-04-02 · in Go Optimization Guide
  21. ▲ 3
    Scala compiler is being rewritten in Go
    story by theboywho · 2025-04-01 · 2 comments
  22. A new sync/v2 NewPool() is being discussed that eliminates the sharp edges by making it generic: https://github.com/golang/go/issues/71076 I haven't personally found it to be problematic; just keep it private, give it a default new func,…
    comment by infogulch · 2025-04-01 · in Go Optimization Guide
  23. Sync.map is meant to have poor performance I believe https://github.com/golang/go/issues/21031
    comment by strangelove026 · 2025-04-01 · in Go Optimization Guide
  24. …usually better to have non-global pools, pool ranges, drop things after a certain capacity, etc.: https://github.com/golang/go/issues/23199 https://github.com/golang/go/blob/7e394a2/src/net/http/h2_bu...
    comment by cplli · 2025-04-01 · in Go Optimization Guide
  25. eventually: https://github.com/golang/go/issues/71076
    comment by arccy · 2025-03-31 · in Go Optimization Guide
  26. Also recent proposal: https://github.com/golang/go/issues/71497
    comment by kristianp · 2025-03-28 · in The Future of JSON in Go (2023) [video]
  27. ▲ 1
    Proposal: Encoding/JSON/v2: new API for encoding/JSON
    story by kristianp · 2025-03-28 · 0 comments
  28. …sum type, but every interface being zeroable seems to be embedded quite deeply in the language. [1] https://github.com/golang/go/issues/57644
  29. …set small. Edited to add: There is this 2023 proposal from Ian Lance Taylor (on the go team) https://github.com/golang/go/issues/57644 But it makes all sum types include nil, which seems suboptimal
  30. …quic is in testing in http://pkg.go.dev/golang.org/x/net/quic and http3 is being implemented https://github.com/golang/go/issues/70914 Since Go has strong backwards compatibility guarantees, they're unlikely to commit to APIs that may need…
    comment by arccy · 2025-03-17 · in HTTP/3 is everywhere but nowhere
  31. …better Go language support exists. [1]: https://pkg.go.dev/github.com/go-json-experiment/json [2]: https://github.com/golang/go/issues/71497 [3]: https://github.com/golang/go/discussions/63397
  32. ▲ 2
    Cmd/compile: slow escape analysis in large package in the TypeScript compiler
    story by mariuz · 2025-03-13 · 0 comments
  33. …magical types for the compiler. Hence why the only thing you will see here is mostly documentation, https://github.com/golang/go/blob/master/src/unsafe/unsafe.g... Which is nothing new since the 1960's that there are systems languages with…
    comment by pjmlp · 2025-03-12 · in A 10x Faster TypeScript
  34. It's not just system calls. E.g. reflection package uses unsafe too: https://github.com/golang/go/blob/master/src/reflect/value.g... . Many packages from Go standard library use unsafe one way or the other, so it's not fair to say that…
    comment by nasretdinov · 2025-03-12 · in A 10x Faster TypeScript
  35. …is not obligated to provide; and (B) WasmGC does not support interior pointers, which Go requires. https://github.com/golang/go/issues/63904#issuecomment-22536...
    comment by mappu · 2025-03-11 · in A 10x Faster TypeScript
  36. Unfortunately, OS vendors like microsoft are quite incompetent at running root stores https://github.com/golang/go/issues/65085#issuecomment-25699...
  37. …claim that any aspect of the language and its standard library is perfect. The many open issues on https://github.com/golang/go attest to that. One example, if I may: the errors.As function is far from ergonomic. It would have been much…
    comment by jub0bs · 2025-03-06 · in The cost of Go's panic and recover
  38. …trying to crack the nut. There is, as of about a month ago, even now an exploratory implementation: https://github.com/golang/go/discussions/71460 It is not an easy nut to crack. Many serious proposals have failed for good reasons. But it…
    comment by 9rx · 2025-03-05 · in The cost of Go's panic and recover
  39. …also like how golang docs literally describe using panics as poor man's exceptions: And I like how https://github.com/golang/go/issues/26799 describes that use of panic in the original version of this bog entry from 2010: quote: However,…
    comment by usrbinbash · 2025-03-04 · in The cost of Go's panic and recover
  40. A similar issue in Go, that I've encountered in real code: https://github.com/golang/go/issues/27505#issuecomment-71370... In a nutshell, if you want to use the death signal, which is very handy and useful, you also need to lock an OS…
    comment by jerf · 2025-02-24 · in Tokio and Prctl = Nasty Bug
  41. ▲ 8
    Poor spill decisions making code 14% slower
    story by mwsherman · 2025-02-22 · 0 comments
  42. AFAIK, the basic issue is still open at https://github.com/golang/go/issues/33803 and https://github.com/golang/go/issues/59715 . You still need to use a helper library like https://github.com/KimMachineGun/automemlimit or…
    comment by lenkite · 2025-02-19 · in One year after switching from Java to Go
  43. …soon are quite low. [1] https://learn.microsoft.com/en-us/windows/win32/fileio/maxim... [2] https://github.com/golang/go/issues/69853
    comment by fowl2 · 2025-02-18 · in Microsoft Go 1.24 FIPS changes
  44. Unfortunately Go doesn’t support exporting DWARF for WASM atm, so printf is the only option. https://github.com/golang/go/issues/33503
    comment by smetannik · 2025-02-14 · in Extensible WASM Applications with Go
  45. How did you miss: https://github.com/golang/go/issues/71134
    comment by wjfuasdf · 2025-02-14 · in Extensible WASM Applications with Go
  46. > I guess my question is, why is Go compelling as a source language for WASM? It's not currently: https://github.com/golang/go/issues/71134
    comment by wjfuasdf · 2025-02-14 · in Extensible WASM Applications with Go
  47. …by volunteers, not the Go team, so timelines are dependent on availability of volunteers. [0]: https://github.com/golang/go/issues/65333#issuecomment-22336...
    comment by boomskats · 2025-02-14 · in Extensible WASM Applications with Go
  48. …for now. Discussion thread here[0]. Might be for the best, with wasip3 just around the corner. [0]: https://github.com/golang/go/issues/66984#issuecomment-20762...
    comment by boomskats · 2025-02-14 · in Extensible WASM Applications with Go
  49. The best part is that it wasn't even an original name within the domain of programming languages: https://github.com/golang/go/issues/9
    comment by Lammy · 2025-02-12 · in DeaDBeeF: The Ultimate Music Player
  50. What would be an use case for `os.Root`? Based on my understanding ( https://github.com/golang/go/issues/67002 ), it is related to security. However, under the hood, it doesn't use `Chroot`, so I could imagine, that eventually someone…
    comment by Hixon10 · 2025-02-12 · in Go 1.24 Is Released