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. …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
  2. …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
  3. 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
  4. …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
  5. Unfortunately, OS vendors like microsoft are quite incompetent at running root stores https://github.com/golang/go/issues/65085#issuecomment-25699...
  6. …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
  7. …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
  8. …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
  9. 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
  10. 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
  11. …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
  12. 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
  13. How did you miss: https://github.com/golang/go/issues/71134
    comment by wjfuasdf · 2025-02-14 · in Extensible WASM Applications with Go
  14. > 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
  15. …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
  16. …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
  17. 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
  18. 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
  19. …slower than native speed, significantly more so than than the equivalent slowdown for c/rust. see https://github.com/golang/go/issues/65440
  20. There are some discussions to add optional generational regions to Go: https://github.com/golang/go/discussions/70257
  21. …when has that stopped go? “[]rune(someString)” is O(n) and quite inobvious The O(n) loop is here: https://github.com/golang/go/blob/215de81513286c010951624243...
    comment by TheDong · 2025-02-09 · in Go Data Structures: Interfaces (2009)
  22. …for the steps to run and comparisons to make. Often you compare actual output with golden data. ( https://github.com/golang/go/tree/master/src/cmd/go/testdata... ) The tools have been extracted and made installable from here:…
    comment by verdverm · 2025-02-08 · in Show HN: Chez Scheme txtar port from Go
  23. Amusingly in go 1.24 they're turning srand into a nop: https://github.com/golang/go/issues/67273
  24. https://github.com/golang/go/issues/69536?ref=words.filippo.... https://words.filippo.io/dispatches/fips-hkdf/ Thought one of the Filippo/Go/FIPS posts had a big thread but doesn't look like it and/or can't find it.
    comment by pvg · 2025-02-06 · in Microsoft Go 1.24 FIPS changes
  25. …correct in assuming it's security theater at best, and an avenue for new backdoors at worst. [1] https://github.com/golang/go/issues/69536
    comment by yalue · 2025-02-06 · in Microsoft Go 1.24 FIPS changes
  26. …Linux 3.0. Microsoft Go fork: https://github.com/microsoft/go Issue discussing FIPS implementation: https://github.com/golang/go/issues/69536
    comment by infogulch · 2025-02-06 · in Microsoft Go 1.24 FIPS changes
  27. The mechanism was reported last year: https://github.com/golang/go/issues/66653 but not acted on.
  28. …one, and it's just including this tiny "Make.dist" file that does nothing except invoke "go tool": https://github.com/golang/go/blob/master/src/Make.dist Wow. So useful. I clicked on the Rust one, and not only did it seem to be specific to…
    comment by coder543 · 2025-01-31 · in A better build system for OCaml
  29. …Rust https://github.com/rust-lang/rust/blob/master/tests/run-make... Go https://github.com/golang/go/blob/master/src/runtime/Makefil... NodeJS https://github.com/nodejs/node/blob/main/Makefile OCaml https://github.com/ocaml/ocaml/
    comment by dumah · 2025-01-31 · in A better build system for OCaml
  30. I created a new package for Multi-dimensional Tensor on Complex Numbers, since https://github.com/golang/go/issues/41129 and other similar attempts didn't work out. My need for such a Tensor package stems from my attempt to create this…
  31. …and now look completely natural. https://research.swtch.com/vgo-principles > type Duration int64 https://github.com/golang/go/blob/519c0a2323700934cbec97b75d... > default values https://gotipplay.golang.org/p/jS6wwznSR7F
    comment by jrimbault · 2025-01-31 · in Go Is a Well-Designed Language
  32. …domain-oriented objects, which is nice. Edit: looks like optional chaining is a separate proposal – https://github.com/golang/go/issues/42847
  33. …well enough and I frankly don't need see any benefits compared to it in this new approach. [1] https://github.com/golang/go/issues/42088
  34. UPD: check this github comment. https://github.com/golang/go/issues/48429#issuecomment-26184... basically it go tool relies heavily on go module pruning, so transitive dependencies from tools are not propagated downstream. also, official…
  35. …not propagate through the dependency tree downstream due to go module pruning check this comment: https://github.com/golang/go/issues/48429#issuecomment-26184... official docs: https://tip.golang.org/doc/modules/managing-dependencies#too...…
  36. proposal is closed and accepted by Go team. [~sigh] you can still leave comments in discussion issue: https://github.com/golang/go/issues/48429
  37. For the dev progress: https://github.com/golang/go/issues/54766
    comment by hencoappel · 2025-01-27 · in Maps are faster in Go 1.24
  38. …the whole service. Unless you're the default `net/http` library and simply recover from the panic: https://github.com/golang/go/blob/master/src/net/http/server...
  39. The difference between compiled code vs the code you wrote makes behaviours non-obvious. https://github.com/golang/go/issues/69887
  40. …from virtual memory in order to make any future accesses an error instead of a use-after-free bug. https://github.com/golang/go/issues/51317
  41. …know about it. Here is a relevant line from Go, even with a comment that it's about overflow: https://github.com/golang/go/blob/19e9231/src/sort/search.go...
  42. …101.org/blog/2024-03-01-for-loop-semantic-changes-... (It is long. A short important summary is here: https://github.com/golang/go/issues/66156 ) Currently (Go 1.24), the official team has not published a tool to identify all of the…
    comment by tapirl · 2025-01-03 · in Go Upgrade Checklist
  43. …breaks, and I can only remember one regression caused by a breaking change in a library[1]. [1] https://github.com/golang/go/issues/24211
    comment by physicles · 2025-01-02 · in Go Upgrade Checklist
  44. I fixed a single word typo in a doc string in github.com/golang/go, resulted in a CONTRIBUTORS entry and a endless torrent of spam from "headhunters".
  45. …an error, Go will just let you ignore it. This is a big issue with treating errors as values. https://github.com/golang/go/issues/20803
    comment by Capricorn2481 · 2024-12-19 · in Idiomatic Errors in Clojure
  46. …concurrent GCs are hard. For interfaces, the Go team chose one of a number of possible solutions: https://github.com/golang/go/issues/8405 If the language were to add support for union types, these tradeoffs could potentially be revisited.…
  47. …"tls: unknown certificate authority")): // handle unexported go stdlib error, XXX fix after https://github.com/golang/go/issues/35234 default: panic(fmt.Sprintf("unhandled error type: %v: %T", err, err)) } Like, for being a statically…
  48. …memory safe. However, once you start using goroutines there can be memory corruption and segfaults: https://github.com/golang/go/issues/37484 . Note that these are not recoverable panics (such as "writing to a close channel"), but causes…
    comment by judofyr · 2024-12-07 · in Weak pointers in Go: why they matter now
  49. …As for first entry, this has been discussed many times without ever reaching any consensus, see - https://github.com/golang/go/issues/19412
  50. …[1] https://github.com/jfhamlin/muscrat [2] https://pkg.go.dev/plugin [3] https://github.com/golang/go/issues/19282 [4] https://github.com/glojurelang/glojure/tree/808165fdc7e65672...