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. …portable: ///usr/bin/env go run "$0" "$@"; exit Note, the exit code isn't passed through due to: https://github.com/golang/go/issues/13440
    comment by emersion · 2025-12-30 · in Go away Python
  2. Official stance about supporting interpreter mode for the reference https://github.com/golang/go/issues/24118
    comment by age123456gpg · 2025-12-30 · in Go away Python
  3. …so seems like a decent chance it will happen. From: #73608 proposal: all: add bare metal support https://github.com/golang/go/issues/73608 > Go applications built with GOOS=none would run on bare metal, without any underlying OS. All…
    comment by typical182 · 2025-12-23 · in Go-boot: bare metal Go UEFI boot manager
  4. https://github.com/golang/go/blob/7ecb1f36acab7b48d77991d58d... Here linker relies on the current memory layout. Changing it requires updating linker code as well.
  5. Issue tracking this “regression” : https://github.com/golang/go/issues/71368
  6. …some open questions like what to use for a backing data type and what complexity promises to make. https://github.com/golang/go/discussions/47331
  7. …isn't sufficient at a technical level, which are brought up by comments on the original proposal: https://github.com/golang/go/issues/21865 1) You are almost certainly going to be passing that key material to some other functions, and…
    comment by kbolino · 2025-12-13 · in Go Proposal: Secret Mode
  8. …You cannot reimplement arenas as the experiment did without special hooks into the runtime. https://github.com/golang/go/blob/master/src/arena/arena.go
    comment by 9rx · 2025-12-11 · in Golang's big miss on memory arenas
  9. TIL: https://github.com/golang/go/discussions/70257
    comment by pstuart · 2025-12-10 · in Golang's big miss on memory arenas
  10. …regions proposal[1], which is what came out of what was learned from tinkering with arenas. [1] https://github.com/golang/go/discussions/70257
    comment by 9rx · 2025-12-10 · in Golang's big miss on memory arenas
  11. …on "memory regions" as a successor to the arena concept, without the API "infection" problem: https://github.com/golang/go/discussions/70257
    comment by ideal_gas · 2025-12-10 · in Golang's big miss on memory arenas
  12. …And an in-progress proposal to make these various "bubble" functions have consistent semantics: https://github.com/golang/go/issues/76477 (As an aside, the linked blog series is great, but if you're interested in new Go features, I've…
    comment by dpifke · 2025-12-10 · in Go Proposal: Secret Mode
  13. I thought the recent error proposal was quite interesting even if it didn't go through: https://github.com/golang/go/issues/71528 My hope is they will see these repeated pain points and find something that fits the error/result/enum issues…
    comment by evanmoran · 2025-12-04 · in Thoughts on Go vs. Rust vs. Zig
  14. …I started reading through one of their highlighted examples --- the Go repo ( https://codewiki.google/github.com/golang/go ). This might be the worst high level overview of Go and its repo I've read. Mostly accurate but unhelpfully…
  15. You might find this proposal and the upcoming runtime/secret package interesting. https://github.com/golang/go/issues/21865
    comment by FiloSottile · 2025-11-20 · in Go Cryptography State of the Union
  16. …e.g. with Go projects, the go linker exposes an -x flag Someday, Go programs won't have to do this: https://github.com/golang/go/issues/50603
    comment by ignoramous · 2025-11-20 · in Reproducible C++ builds by logging Git hashes
  17. …been working on a programming language named Go for the last 10 years, please pick another name." https://github.com/golang/go/issues/9
    comment by CobrastanJorji · 2025-11-17 · in Project Gemini
  18. …and when they did Go! dirty, Google made clear which one they are. Status changed to Unfortunate https://github.com/golang/go/issues/9#issuecomment-66047478
    comment by ModernMech · 2025-11-15 · in Go's Sweet 16
  19. …something like intrinsics even. Fortunately compiler support for intrinsics seems to be on its way! https://github.com/golang/go/issues/73787
    comment by ashf023 · 2025-11-05 · in The state of SIMD in Rust in 2025
  20. …to technical infeasibilty. What exactly are the rules for when a thread is garbage collected in W++? [0] github.com/golang/go/issues/19702
    comment by bheadmaster · 2025-10-26
  21. …want to optimistically assume otherwise. Is pread() available in the Golang standard library? https://github.com/golang/go/issues/19563 is someone using os.File.ReadAt, which is a method name that makes me even more uncertain. But there's…
  22. …the code that would be needed, and I discovered that you can't call real or imag on generic types: https://github.com/golang/go/issues/50937 ]
    comment by kbolino · 2025-10-22 · in Go subtleties
  23. The time.After function creates a channel that will be sent a message after x seconds. Or, will it? https://github.com/golang/go/issues/24595 ... even though the value is nil, the type of the variable is a non-nil interface... Go "boxes"…
    comment by ignoramous · 2025-10-22 · in Go subtleties
  24. …System" or "Phone Idle") For example, Golang applications had 15 second keep alive until recently: https://github.com/golang/go/issues/48622 . Imagine you've opened the website which uses golang web server/proxy and enabled notifications…
  25. The consequences of this genius decision were stuff like this: https://github.com/golang/go/issues/16570 Which is why they have already backpedalled on this decision on most platforms. Linux is pretty much the only OS where the syscall ABI…
    comment by int_19h · 2025-10-19 · in IDEs we had 30 years ago and lost (2023)
  26. …you can easily experiment to see if this helps your application, without doing a major refactor. In https://github.com/golang/go/issues/64926 it was a bridge-too-far for the Go developers (fair enough) but maybe it could still happen one…
  27. Semi related: there is an active proposal of having a go OS Target of "none" (or noos (No-OS)). https://github.com/golang/go/issues/73608 Sounds like they want to maybe include https://github.com/usbarmory/tamago in the compiler.
  28. …The reporter actually spent the effort to track it down, turns out it _was_ a Go compiler bug. ( https://github.com/golang/go/issues/20427 )
    comment by SuperQue · 2025-10-09 · in We found a bug in Go's ARM64 compiler
  29. I noticed this when reviewing the linked issue: https://github.com/golang/go/issues/73259#issuecomment-31004... Does the Go team have a natural language bot or is this just comment.contains(“backport”) type stuff?
    comment by cmckn · 2025-10-08 · in We found a bug in Go's ARM64 compiler
  30. For the impatient, here's the fix: https://github.com/golang/go/commit/f7cc61e7d7f77521e073137c...
    comment by pengaru · 2025-10-08 · in We found a bug in Go's ARM64 compiler
  31. …I'm really hopeful that the SIMD proposals do eventually make it into the language, e.g. this one: https://github.com/golang/go/issues/73787#issuecomment-32081...
  32. …hold: > Note, 2023-01-17. This proposal is on hold indefinitely due to serious API concerns. https://github.com/golang/go/issues/51317 Potential successor: https://github.com/golang/go/discussions/70257
  33. …easy to fix if you stumble upon it after years of added cruft and changing requirements. [1]: https://github.com/golang/go/issues/12914
  34. …[2] https://github.com/cloudwego/goref/blob/main/docs/principle.... [3] https://github.com/golang/go/issues/57175
    comment by felixge · 2025-09-23 · in Go has added Valgrind support
  35. https://github.com/golang/go/issues/63904 Skimming this issue, it seems like they weren't expecting to be able to use this GC. I know C# couldn't either, at least based on an earlier state of the proposal.
    comment by davey48016 · 2025-09-17 · in WASM 3.0 Completed
  36. …But there are problems with supported types; see my other comments. 2) It is improved in 1.25. See https://github.com/golang/go/issues/59928 and https://pkg.go.dev/testing#T.Output . Now it is possible to update slogt to provide correct…
  37. …And some previous discussion. Frustrating! - https://pkg.go.dev/log/slog#example-package-Wrapping - https://github.com/golang/go/issues/59145#issuecomment-14770...
    comment by peterldowns · 2025-09-12 · in Logging in Go with Slog: A Practitioner's Guide
  38. Go doesn't yet have native SIMD support, but it actually might in the future: https://github.com/golang/go/issues/73787 I think when it's introduced it might be worth discussing that again. Otherwise providing assembly for JSON of all…
    comment by nasretdinov · 2025-09-09 · in A new experimental Go API for JSON
  39. …and reach a consistent solution (or as close as possible). This has been my favorite for a while: https://github.com/golang/go/issues/45624 4 years to decide on something relatively minor, that right now can be done with a bit of a…
  40. …to copy some files somewhere else, and then delete the directory. Unfortunately, you hit this https://github.com/golang/go/issues/32334 oops, looks like some files are just inaccessible to you, and you cannot copy them. Fortunately, when…
    comment by xyzzyz · 2025-08-23 · in Go is still not good
  41. …considered ownership semantics [2] Notable mentions: - No sum types - No string interpolation [1]: https://github.com/golang/go/issues/19623 [2]: https://news.ycombinator.com/item?id=39477821
    comment by Mawr · 2025-08-22 · in Go is still not good
  42. …and try to link with an application, you will have a terrible time. I've ran into this same issue: https://github.com/golang/go/issues/65050 https://www.youtube.com/watch?v=xuv9A7CJF54&t=440s
    comment by metaltyphoon · 2025-08-22 · in Go is still not good
  43. …strings or interfaces meet the alignment requirements. [1]: https://research.swtch.com/gorace [2]: https://github.com/golang/go/issues/61236 [3]: https://pkg.go.dev/github.com/CAFxX/atomic128
    comment by kbolino · 2025-08-22 · in Go is still not good
  44. …and "slices.Sort", "atomic.Pointer" and "atomic.Value", quite possible a sync/v2 soon https://github.com/golang/go/issues/71076 , etc. The old non-generic versions also aren't deprecated typically, so they're just there to trap people that…
    comment by TheDong · 2025-08-22 · in Go is still not good
  45. …clocks and every go program written is littered with terrible bugs due to use of the wrong clock https://github.com/golang/go/issues/12914 ( https://github.com/golang/go/issues/12914#issuecomment-15075... might qualify for the worst…
    comment by blibble · 2025-08-22 · in Go is still not good
  46. …isn't invalid UTF-8 but invalid UTF-16 (on Windows et al). AIUI Go had nasty bugs around this ( https://github.com/golang/go/issues/59971 ) until it recently adopted WTF-8, an encoding that was actually invented for Rust's OsStr. WTF-8 has…
    comment by duckerude · 2025-08-22 · in Go is still not good
  47. …is at least memory-aware, in that it endeavors to process objects close to one another together." https://github.com/golang/go/issues/73581
    comment by theobeers · 2025-08-22 · in Go is still not good
  48. …Being hungry and in a hurry doesn't help with remembering names. The GitHub discussion is there: https://github.com/golang/go/discussions/58409 but the words I of Russ I cited is here: https://groups.google.com/g/golang-dev/c/73vJrjQTU1M/m/…
    comment by bayindirh · 2025-08-19 · in "Remove mentions of XSLT from the html spec"
  49. A few more links that I collected recently on the topic https://github.com/golang/go/issues/73626 https://developer.mozilla.org/en-US/docs/Web/Security/Attack... https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/...…
    comment by nchmy · 2025-08-13 · in Cross-Site Request Forgery
  50. So now there is at least a workaround to preserve the order when processing JSON. Great! [1] https://github.com/golang/go/issues/27179#issuecomment-22899...
    comment by kvemkon · 2025-08-13 · in Go 1.25 Release Notes