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
AllStoriesComments NewestTopOldest
  1. …when 'regions' are introduced, which have similar performance benefits but a much lower API impact: https://github.com/golang/go/discussions/70257 As discussed there, seeing how people actually used the arena GOEXPERIMENT influenced the…
    comment by typical182 · 2025-08-13 · in Go 1.25 Release Notes
  2. If you look at the github issue related to the PR, you'll see some examples: https://github.com/golang/go/issues/56025#issuecomment-20667... Looks like the original poster on that thread is making it because Mailgun uses Go, and was…
    comment by TheDong · 2025-08-13 · in Go 1.25 Release Notes
  3. …the bug which was blogged about in "How we tracked down a Go 1.24 memory regression" [2,3]. [1] https://github.com/golang/go/issues/72991 [2] https://www.datadoghq.com/blog/engineering/go-memory-regress... [3]…
    comment by kristianp · 2025-08-13 · in Go 1.25 Release Notes
  4. > greentea I didn't know what it is and had to look it up. Looks like a new GC. https://github.com/golang/go/issues/73581
    comment by latchkey · 2025-08-12 · in Go 1.25 Release Notes
  5. 1.25 tag was released; https://github.com/golang/go/releases/tag/go1.25.0
    comment by bitbasher · 2025-08-12 · in Go 1.25 Release Notes
  6. …for func/fn and explicit return. Because the arrow would break stuff is one of the reasons. See https://github.com/golang/go/issues/59122 https://github.com/golang/go/issues/21498 res := is.Map(func(i int)int{return i+1}).Filter(func(i…
    comment by lenkite · 2025-08-10 · in Zig's Lovely Syntax
  7. …author replies they don't do that because the lack of inference makes for nasty boilerplate ( https://github.com/golang/go/issues/34510#issuecomment-53961... ).
    comment by masklinn · 2025-08-09 · in A subtle bug with Go's errgroup
  8. …shadowed `ctx` variable. There is an old issue in the tracker proposing changes to alleviate this: https://github.com/golang/go/issues/34510 . The original author (bcmills) of the errgroup package shared insight into the design…
    comment by dantillberg · 2025-08-09 · in A subtle bug with Go's errgroup
  9. …believe are just there to track dependencies that are not in the project, or to help with caching: https://github.com/golang/go/issues/36460 In go 1.17 they were added so that project loading did not require downloading the go.mod of every…
    comment by maxmcd · 2025-08-06 · in We shouldn't have needed lockfiles
  10. …But thank you for pointing that out. TIL, there's a single epoll queue for the whole Go process: https://github.com/golang/go/issues/65064
    comment by wahern · 2025-07-25 · in Superfunctions: A universal solution against sync/async fragmentation in Python
  11. https://github.com/golang/go/issues/34902 https://www.cloudfoundry.org/blog/cve-2020-15586/ I don’t see any evidence that anyone wrote an RCE exploit for this, but I also don’t see any evidence of anyone even trying to rule it out.
    comment by amluto · 2025-07-24 · in There is no memory safety without thread safety
  12. …functions is moved onto the heap because interface{} is always counted as escaped from the stack ( https://github.com/golang/go/issues/8618 ).
    comment by fsmv · 2025-07-22 · in Go allocation probe
  13. …stuff? Probably not. This is usually done with EF Core and the Postgres provider. [0] https://github.com/golang/go/issues/51317 [1] https://www.nuget.org/
    comment by database64128 · 2025-07-20 · in C# Language Design Meeting for June 30th, 2025
  14. The trade off is discussed here: https://github.com/golang/go/issues/70835
    comment by aaronbee · 2025-07-20 · in How we tracked down a Go 1.24 memory regression
  15. …doesn't have it yet. Go is headed strongly in that direction which is why I add the "yet", but see https://github.com/golang/go/issues/70128 , especially the "future directions" note about issue #48522 which is not implemented. Prepatory…
    comment by jerf · 2025-07-18 · in Row Polymorphic Programming
  16. …And the change makers even have no interests to fix the problems caused by the changes: * https://github.com/golang/go/issues/66070#issuecomment-19816... * https://github.com/golang/go/issues/71830 * https://github.com/spq/pkappa2/issues/23…
    comment by tapirl · 2025-07-10 · in Generic interfaces
  17. …so they become more widely known. The standard library is just starting to add generic containers: https://github.com/golang/go/issues/69559 And part of that is discussing how we want to do things like this:…
    comment by Merovius · 2025-07-08 · in Generic interfaces
  18. It's heavily used where you need performance, for example crypto. https://go.dev/wiki/AssemblyPolicy https://github.com/golang/go/tree/master/src/crypto/internal...
    comment by Thaxll · 2025-06-23 · in How to store Go pointers from assembly
  19. …bump to v1.21.5 means it will only work on more recent computers and Win10 and 11 for no benefit. https://github.com/golang/go/issues/64622
    comment by pidgeon_lover · 2025-06-13 · in Show HN: I wrote a BitTorrent Client from scratch
  20. …heart of it all, it's all just the same. Here are enum implementations in both Go and Rust: [Go] https://github.com/golang/go/blob/f18d046568496dd331657df4ba... [Rust] https://github.com/rust-lang/rust/blob/40daf23eeb711dadf140b... While…
    comment by 9rx · 2025-06-10 · in Go is a good fit for agents
  21. …you import the os package, on startup, the open file soft limit will be raised to the hard limit: https://github.com/golang/go/commit/8427429c592588af8c49522c...
    comment by database64128 · 2025-06-06 · in Too Many Open Files
  22. …to leave the status quo as-is is probably one of the most favorably voted Go proposals of all time: https://github.com/golang/go/issues/32825 Go language design is not a popularity contest or democracy (if nothing else because it is not…
    comment by Merovius · 2025-06-04 · in (On | No) Syntactic Support for Error Handling
  23. …in this case. The most popular Go proposal/issue of all times was 'leave "if err != nil" alone': https://github.com/golang/go/issues?q=is%3Aissue%20%20sort%3...
    comment by mseepgood · 2025-06-03 · in (On | No) Syntactic Support for Error Handling
  24. …to the wiki page for this: https://go.dev/wiki/Go2ErrorHandlingFeedback or the GitHub issue search: https://github.com/golang/go/issues?q=+is%3Aissue+label%3Aer... I promise that you are not the first to propose whatever you're proposing,…
    comment by threemux · 2025-06-03 · in (On | No) Syntactic Support for Error Handling
  25. Not OP, but I found a compiler bug in the initial release of 1.18, though it was also quickly fixed: https://github.com/golang/go/issues/51733
    comment by kbolino · 2025-06-03 · in (On | No) Syntactic Support for Error Handling
  26. The bug is confirmed: https://github.com/golang/go/issues/71685
    comment by tapirl · 2025-05-29 · in Pure vs. Impure Iterators in Go
  27. …I relatively recently ran into something similar to this on a fresh VM without internet egress: https://github.com/golang/go/issues/68976 https://github.com/golang/go/issues/68946 If golang doesn't fully address this I guess Debian really…
    comment by enfuse · 2025-05-22 · in Why does Debian change software?
  28. Oh heh yes it is. I just remembered the original discussion from 2019 ( https://github.com/golang/go/issues/33803 ) and grepped the source tree for cgroup to see if that got done or not, but didn't check when it got done. As said in 2019,…
    comment by yencabulator · 2025-05-21 · in Understanding the Go Scheduler
  29. 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
  30. 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
  31. …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
  32. 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
  33. 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
  34. …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
    comment by burntsushi · 2025-05-10 · in Rust’s dependencies are starting to worry me
  35. …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.
    comment by krackers · 2025-05-01 · in Mac app launches slowed by malware scan (2024)
  36. …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
  37. …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
  38. 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
  39. …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
  40. …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
  41. …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
  42. 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
  43. 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
  44. 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
  45. …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
  46. eventually: https://github.com/golang/go/issues/71076
    comment by arccy · 2025-03-31 · in Go Optimization Guide
  47. 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]
  48. …sum type, but every interface being zeroable seems to be embedded quite deeply in the language. [1] https://github.com/golang/go/issues/57644
    comment by ajb · 2025-03-26 · in Good-bye core types; Hello Go as we know and love it
  49. …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
    comment by ajb · 2025-03-20 · in Decoding JSON sum types in Go without panicking
  50. …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