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. …to all user packages would be a major improvement over the status quo. We have plans to get there. https://github.com/golang/go/issues/32816
  2. …The end of the post they mention that an encoding/json/v2 package is in the works: https://github.com/golang/go/discussions/63397
  3. …acknowledgement, but here are some counterexamples: - A proposal for sum types by a Go team member: https://github.com/golang/go/issues/57644 - The community proposal with some comments from the Go team:…
  4. …is the need to return zero values of all the declared function return types along with the error: https://github.com/golang/go/issues/21182 .
  5. There used to be the GO FIPS branch: https://github.com/golang/go/tree/dev.boringcrypto/misc/bori... But it looks dead for some time. However https://github.com/golang-fips/go sprung up to take it's place. I wonder why microsoft prefers to…
  6. Go version is pretty good: https://github.com/golang/go/blob/go1.22.2/src/net/netip/net...
  7. ▲ 3
    We now have crypto/rand back ends that ~never fail
    story by weinzierl · 2024-04-14 · 1 comment
  8. …deliberately ignored this on the assumption that they can get away with it. And then this happened: https://github.com/golang/go/issues/16606 If that's not "getting burned", I don't know what is. "Trying to provide a nice feature" is an…
    comment by int_19h · 2024-04-07 · in OpenBSD 7.5
  9. …to add them to the language have revealed deep issues that have stalled any development. See https://github.com/golang/go/issues/57644
    comment by spenczar5 · 2024-04-05 · in Go's Error Handling Is Perfect
  10. …enough to not set off the same alarm bells. The best example of this is probably this GitHub issue: https://github.com/golang/go/issues/19991 (though there are countless like it). I’ve worked with Tony Arcieri, he’s brilliant and humble…
    comment by benreesman · 2024-03-28 · in Go Enums Still Suck
  11. …by people who believe syntax highlighting is useless, of course they decided against generics… [0] https://github.com/golang/go/commit/7d7c6a97f815e9279d08cfae...
    comment by littlestymaar · 2024-03-24 · in Fault tolerance and resilience patterns for Go
  12. At least one Go crypto developer publicly expressed concern about this very issue in 2021: https://github.com/golang/go/issues/49702
  13. …an interesting conversation by the Go developers from as early as 2021 being suspicious of DIT: https://github.com/golang/go/issues/49702
  14. That's not really what clear is for. See https://github.com/golang/go/issues/21865
    comment by yencabulator · 2024-03-15 · in Programs written in Golang have no secrets
  15. …that does blocking read on the Pipe and then pass it on to another channel to select on. [1] https://github.com/golang/go/issues/66239 [2] https://github.com/scratchdata/scratchdata/blob/7c1a0fcd0e20... [3]…
  16. related: https://github.com/golang/go/issues/51317
  17. And they now have to deal with the same kind of timing attacks related stuff as everybody else https://github.com/golang/go/issues/49702 (and they'll likely lag behind)
  18. Of course it does: just call TCPConn.SetNoDelay(false). See https://github.com/golang/go/blob/master/src/net/tcpsock.go#...
  19. It is not like Go wasn't already taken. https://github.com/golang/go/issues/9
  20. …interesting way: It is out of scope of the current proposal to write anything to the original tail https://github.com/golang/go/issues/63393
    comment by everybodyknows · 2024-02-24 · in Go(lang): Robust generic functions on slices
  21. …in July of 2022 that Go did exactly the vulnerable example and reported it to the security team. https://github.com/golang/go/issues/53849 It was fixed as of Go 1.21 https://go.dev/doc/go1.21 --- The article cites JavaScript, which is not…
  22. …[subprocess flags] before that it was just > go run [go flags] [*.go-list] [subprocess flags] [1] https://github.com/golang/go/issues/22726
    comment by SPBS · 2024-02-22 · in Go run
  23. …pretty interesting blog post[1] and discussion[2]. 1: https://research.swtch.com/telemetry-intro 2: https://github.com/golang/go/discussions/58409
  24. …implemented? Go is open source, you can see for yourself, channels still use mutexes internally. https://github.com/golang/go/blob/b6ca586181f3f1531c01d51d63... If you needed one mutex lock to receive a reference to a data structure, a…
    comment by fl0ki · 2024-02-15 · in Maybe Everything Is a Coroutine
  25. It's not a hard rule that context should not be struct fields. See https://github.com/golang/go/issues/22602 (context: relax recommendation against putting Contexts in structs) "Right now the context package documentation says > Do not…
    comment by SPBS · 2024-02-09 · in Context Control in Go
  26. Rule 3: Don’t store contexts - What about this: https://github.com/golang/go/blob/master/src/net/http/client... req = &Request{ Method: redirectMethod, Response: resp, URL: u, Header: make(Header), Host: host, Cancel: ireq.Cancel, ctx:…
    comment by italicmew123 · 2024-02-09 · in Context Control in Go
  27. Is the memory issue reported in go 1.21 version in linux OS resolved in go 1.22? https://github.com/golang/go/issues/64332
    comment by ihtkas · 2024-02-08 · in Go 1.22
  28. Server 2012 was dropped in https://github.com/golang/go/issues/57004 and it's still in security support. My numbers are somewhat similar to @olivielpeau in that thread.
    comment by mappu · 2024-02-07 · in Go 1.22
  29. …this bug: "Unable to reliably distinguish IPv4-mapped-IPv6 addresses from regular IPv4 addresses" https://github.com/golang/go/issues/37921 . Use https://pkg.go.dev/net/netip instead.
  30. ▲ 1
    Golang can't decode certain jpgs (2013)
    story by itake · 2024-01-24 · 0 comments
  31. …some time this year. 0. https://bgammon.org 1. https://bgammon.org/blog/20240101-hello-world/ 2. https://github.com/golang/go/issues/28631
  32. …constructs, I would never be able to trust something like this to store and restore my code. [1] https://github.com/golang/go/issues/20744 [2] https://github.com/dtolnay/syn/issues/782
  33. …resistance to bugs doesn't appear to be a priority even for the Go team itself (e.g. even recently https://github.com/golang/go/issues/64474 )
  34. This one bug greatly undermined my confidence in Go forever: https://github.com/golang/go/issues/64474 That this can happen in the standard library and stay in a stable release for 5-6 months, in fact very nearly making it to Go 1.22,…
    comment by fl0ki · 2024-01-10 · in Go 1.21.6 Released
  35. …so how could this possibly yield a performance improvement? It turns out, with some more research ( https://github.com/golang/go/issues/25819 ), that the function was added not to guarantee performance but to guarantee precision , namely…
  36. …interpreted Go REPL) have "know limitations, won't be addressed" also because of these assumptions. https://github.com/golang/go/issues/4146 https://github.com/golang/go/issues/16522 https://github.com/traefik/yaegi?tab=readme-ov-file#limit…
    comment by ncruces · 2024-01-05 · in Go: What we got right, what we got wrong
  37. For reference, the GitHub thread is: https://github.com/golang/go/issues/12914
    comment by tubthumper8 · 2024-01-05 · in Go: What we got right, what we got wrong
  38. …to monotonic time in any way. It had that feature internally, just gave no way to access it (hence https://github.com/golang/go/issues/16658 ).
    comment by masklinn · 2024-01-05 · in Go: What we got right, what we got wrong
  39. …[2]: https://groups.google.com/g/golang-nuts/c/UgbTmOXZ_yw/m/NH0j... [3]: https://github.com/golang/go/tree/weekly.2011-01-12/src/pkg/...
    comment by unscaled · 2024-01-05 · in Go: What we got right, what we got wrong
  40. …[8]: https://groups.google.com/g/golang-nuts/c/qKB9h_pS1p8/m/1NlO... [9]: https://github.com/golang/go/issues/13761#issuecomment-16772... [10]: https://go.dev/talks/2011/Real_World_Go.pdf (Slide #25)
    comment by unscaled · 2024-01-05 · in Go: What we got right, what we got wrong
  41. …those pointers (via a stack map) and adjust them to point to the new stack locations. For example: https://github.com/golang/go/blob/b25f5558c69140deb652337afa... (The growable stacks I think replaced the segmented stacks circa Go 1.3 or…
    comment by typical182 · 2024-01-05 · in Go: What we got right, what we got wrong
  42. …- https://github.com/openssl/openssl/issues/7482 - https://github.com/openssl/openssl/pull/22938 - https://github.com/golang/go/issues/63369
    comment by Ayesh · 2024-01-05 · in Use of HTTPS Resource Records
  43. …to see a crypto maintainer bashing on GnuPG [3] and trying to discredit Dan Bernstein [4]. [1]: https://github.com/golang/go/issues/49269 [2]: https://github.com/go-gitea/gitea/issues/17798 [3]: https://twitter.com/FiloSottile/status/112764…
  44. …golang creates a threadpool for running goroutines on platforms that use thread primitives. From https://github.com/golang/go/blob/c7d6c6000a84b61ac8bb2e38e8... I believe "worker threads" are OS threads.
  45. …The Go HTTP server does this internally (though there is talk about not doing it, deferred til Go 2 https://github.com/golang/go/issues/5465 ). > The process should crash; the alternative is to continue operating in an unknown,…
    comment by everforward · 2024-01-04 · in Go: What we got right, what we got wrong
  46. …is a really cool data-oriented feature. This is what i imagine Go would look like with that: https://github.com/golang/go/issues/64926
    comment by mappu · 2024-01-02 · in Odin Programming Language
  47. …like recompiling my site while I’m writing. Go templates are fundamentally not what I wanted. [1] https://github.com/golang/go/issues/54748
    comment by bvisness · 2023-12-31 · in LuaX: A Lua Dialect with JSX
  48. …goroutines are implemented, it's because it is a design decision to not allow users to do that. [1] https://github.com/golang/go/issues/22289 [2] https://go.dev/doc/go1.14
    comment by EdiX · 2023-12-31 · in The Downsides of Go's Goroutines
  49. …and contemplate the disaster that gets interpreted from it: [Unmarshal(data []byte, v any)](https://github.com/golang/go/blob/go1.21.0/src/encoding/json/decode.go#L97) (spoiler: it just thinks that the link title is "Unmarshal(data [" and…
  50. …do anything if there isn't memory pressure It will run every 2 minutes, if it hasn't run otherwise https://github.com/golang/go/blob/9b4b3e5acca2dabe107fa2c3ed...
    comment by Yasuraka · 2023-12-19 · in Gokrazy – Go Appliances