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. …non-ELF standard parameters for initialization of supposedly "C ABI" libraries, open since 2015. https://github.com/golang/go/issues/13492 The Go project specifically acknowledging the glibc-isms here: "All Linux first class ports are for…
  2. …who pays the majority of the people working on it? Google? Checking the 20 top contributors from https://github.com/golang/go/graphs/contributors Google: 10 Unclear: 7 Tailscale: 1 Canopy Climate: 1 Isovalent: 1 Just checking the GitHub…
  3. I hate to drag Go into this but I can't help but compare what happened here to the attitude here: https://github.com/golang/go/discussions/55092 My initial impression was that this is boiling the ocean but there's substantial foresight. If…
    comment by xyzzy_plugh · 2024-08-01 · in Rust Just Failed an Important Test
  4. …with C interop. There had been an issue for having something similar in the language itself - https://github.com/golang/go/issues/42469 , but the Golang compiler team rejected it. If you have followed similar discussions around this with…
  5. …the reason they don’t exist in C#. It’s also one of the reasons GO doesn’t have extension methods. https://github.com/golang/go/issues/37742#issuecomment-59616... You either have to exclude extension methods from implicit interface…
    comment by swisniewski · 2024-07-26 · in C# almost has implicit interfaces
  6. …that all Go code looks about the same. That’s simply not true for code with custom iteration. [0] https://github.com/golang/go/discussions/56413
    comment by bheadmaster · 2024-07-14 · in Go range iterators demystified
  7. Here's the tracking issue for Go if you're interested: https://github.com/golang/go/issues/67520 I wouldn't be holding my breath though - proper support of high-level portable SIMD abstraction requires quite a lot of compiler complexity…
  8. …performance is a Go problem rather than a WebAssembly problem. See this issue for more info: https://github.com/golang/go/issues/28631
  9. …platform. When running as a native Android app, all of the device's CPU cores are utilized. 0. https://github.com/golang/go/issues/28631
  10. see for yourself https://github.com/golang/go/commits/master/src/crypto
  11. ▲ 2
    Russ Cox is writing an LLM based bot to help in the Go Issue Tracker
    story by bashtoni · 2024-06-28 · 0 comments
  12. ▲ 27
    Pad jumps to avoid Intel erratum (2019)
    story by userbinator · 2024-06-25 · 0 comments
  13. …the HTTP server can't implement range requests. Interesting comment by Russ Cox about this: https://github.com/golang/go/issues/61791#issuecomment-16719...
    comment by agwa · 2024-06-25 · in MIME, RSS, and Existential Torment
  14. …that prevents them from using `bufio.Peek` though. [1]: Link to the use of Seek, for reference: https://github.com/golang/go/lob/e8ee1dc4f9e2632ba1018610d1a...
    comment by quectophoton · 2024-06-24 · in Interface Upgrades in Go (2014)
  15. https://github.com/golang/go/issues/61901 https://github.com/golang/go/issues/61902 https://github.com/golang/go/issues/61900 https://github.com/golang/go/issues/61899 https://github.com/golang/go/issues/61898 Yes there are and a lot of…
    comment by skldj28d2 · 2024-06-18 · in The upcoming iterator design for Go 1.23
  16. https://github.com/golang/go/issues/61405#issuecomment-16388... : > Can you provide more motivation for range over functions? > If the results can be generated one at a time, then a representation that allows iterating over them scales…
  17. …So now that we know better what Go is about, we can try to see why the iterators are added. From https://github.com/golang/go/issues/61405#issuecomment-16388... . I'll quote some parts: > Can you provide more motivation for range over…
  18. …doing generics too with code generation but that was probably less doable for library code...) [1]: https://github.com/golang/go/discussions/56413
    comment by jkrejcha · 2024-06-18 · in The upcoming iterator design for Go 1.23
  19. …the Go module proxy stores the malicious copy. There are other tricks an attacker can play as well: https://github.com/golang/go/issues/66653 Ultimately, if you're doing a code audit, you have to compute the checksum of the code that…
  20. …Windows has IOCPs, Linux has io_uring, FreeBSD has kqueue, POSIX has... POSIX AIO, etc. [2]: https://github.com/golang/go/issues/31908 [3]: https://github.com/golang/go/issues/6817
    comment by jkrejcha · 2024-06-13 · in Swift Static Linux SDK
  21. ▲ 1
    Orbail proposal for go error handling
    story by aredirect · 2024-06-12 · 0 comments
  22. > The Go database/sql package actually executes ROLLBACK in the SQL engine. No: https://github.com/golang/go/blob/beaf7f3282c2548267d3c89441...
    comment by owl57 · 2024-06-11 · in A ChatGPT mistake cost us $10k
  23. There is a version 2 being implemented to fix some of the known issues. https://github.com/golang/go/discussions/63397 https://pkg.go.dev/github.com/go-json-experiment/json
  24. Ah ha! So the issue was always going through the error type reflection even for the success path. https://github.com/golang/go/commit/af43932c20d5b59cdffca454... I'd be interesting to see the benchmark after that.
  25. …take away is that the question has been kicked off: can wrapped errors be made more efficient? 1. https://github.com/golang/go/commit/af43932c20d5b59cdffca454...
  26. Nice find. This commit: https://github.com/golang/go/commit/af43932c20d5b59cdffca454... from April 4.
  27. …which would explain the significant performance cost. If err is nil, it doesn't return early. https://github.com/golang/go/blame/adbfb672ba485630d75f8b559...
  28. …and unnecessary reflection. Perhaps 1.23, or whichever release that ends up in, would be faster? https://github.com/golang/go/commit/af43932c20d5b59cdffca454...
  29. …first 3 lines of `errors.is` [0] are the following: if target == nil { return err == target } [0]: https://github.com/golang/go/blob/go1.22.3/src/errors/wrap.g...
  30. …a separate function if the compiler would inline Is() reducing the perf impact. Possibly related: https://github.com/golang/go/issues/61502 Looks like they're working on improving the inliner.
  31. …`errors.Is()` [0] are the following: if err == nil || target == nil { return err == target } [0]: https://github.com/golang/go/blob/9b43bfbc51c469ec13fca24960...
  32. …obvious once you read the code—it relies on reflection followed by a tree-walking algorithm. [0]: https://github.com/golang/go/blob/9b43bfbc51c469ec13fca24960...
  33. …by adding a check for `err == nil && target != nil` and vice versa, rather than `err == target`? https://github.com/golang/go/blob/9b43bfbc51c469ec13fca24960...
  34. …get you 10% in some cases. Shameless plug: We recently GA'ed our support for it at Datadog [3]. [1] https://github.com/golang/go/issues/54766 [2] https://go.dev/doc/pgo [3] https://www.datadoghq.com/blog/datadog-pgo-go/
    comment by felixge · 2024-05-30 · in Fast Shadow Stacks for Go
  35. …good idea for the runtime until hardware shadow stacks become widely available and accessible. [1] https://github.com/golang/go/issues/57175
    comment by felixge · 2024-05-30 · in Fast Shadow Stacks for Go
  36. Did you get any response from Go core team? Might make sense to open issue in GitHub https://github.com/golang/go/issues/ and start thread in https://groups.google.com/g/golang-dev
    comment by nikolayasdf123 · 2024-05-30 · in Fast Shadow Stacks for Go
  37. …in this way so the same algorithm can be used to implement the various existing sort APIs. https://github.com/golang/go/blob/master/src/sort/gen_sort_v...
  38. …know pretty soon from failing tests of their own Wasm/WASI toolchain. https://go.dev/blog/wasi https://github.com/golang/go/blob/go1.22.3/misc/wasm/go_wasi... As for sandboxing, wazero tends to take sandboxing rather more seriously than…
  39. …been around this loop multiple times now with people, here is the source code for go:generate: https://github.com/golang/go/blob/master/src/cmd/go/internal... I've highlighted the line where it executes the given command. This is not aimed…
  40. it's a known issue https://github.com/golang/go/issues/31866
    comment by arccy · 2024-05-25 · in Abusing Go's Infrastructure
  41. …but older tar programs still allow that. And programs written in Go, because of course: https://github.com/golang/go/issues/55356 Overall, if your HDD size is infinite and you're using GNU tar, or another recent tar, you can skip 't' I…
    comment by TheDong · 2024-05-24 · in How to destroy your OS with tar
  42. ▲ 1
    Proposal: Add "SIMD" package to standard library
    story by mfiguiere · 2024-05-20 · 0 comments
  43. https://github.com/golang/go/issues/57530
    comment by fdefilippo · 2024-05-20 · in Golang is evil on shitty networks
  44. …was always the default in Golang. Enable TCP_NODELAY => "disable Nagle's algorithm") [1] https://github.com/golang/go/issues/57530
    comment by supriyo-biswas · 2024-05-10 · in It's always TCP_NODELAY
  45. …it's not like it's a regular occurrence for Linux to new functions to the vDSO, in any case. [0] https://github.com/golang/go/blob/master/src/runtime/time_li...
    comment by LegionMammal978 · 2024-05-09 · in It's always TCP_NODELAY
  46. https://news.ycombinator.com/item?id=34179426 https://github.com/golang/go/issues/57530 huh, TIL.
    comment by andrewfromx · 2024-05-09 · in It's always TCP_NODELAY
  47. …ASM dialect at much greater effort for a specific platform. For example, Go has to resort to this https://github.com/golang/go/blob/4ed358b57efdad9ed710be7f4f... in order to efficiently scan memory, while in C# you write the following once…
    comment by neonsunset · 2024-05-08 · in Arena-based parsers
  48. It is probably not related, but gopls has a known issue with its heuristic for picking imports: https://github.com/golang/go/issues/61208
    comment by meling · 2024-05-07 · in Secure Randomness in Go 1.22
  49. …out the syscalls do not actually fail in practice (it's not possible to "run out of entropy"): https://github.com/golang/go/issues/66821
    comment by agwa · 2024-05-07 · in Secure Randomness in Go 1.22
  50. …somewhat. Here is the issue for slow sax parsing in encoding/xml. No work on it since around 2020: https://github.com/golang/go/issues/21823
    comment by kristianp · 2024-05-07 · in Faster XML Stream Processing in Go (2019)