News for hackers. Stuff that matters.

A comment on Major standard library changes in Go 1.20. Parent comment

Re:Major standard library changes in Go 1.20 by eptcyka on Tuesday January 17, 2023 @03:20AM (#34410281)
Why do Go enthusiasts look at types that specialize more generic data structures to ensure invariants and scoff? Maybe go only ever needed []byte, and nothing else - it's always just bytes anyway, right?

Moreover, when the go team accomplishes the same goals by extending the language instead of using a library, this is well received.

[ Parent | on HN ]
Re:Major standard library changes in Go 1.20 by stickupkid on Tuesday January 17, 2023 @04:58AM (#34410825)
Specifically to the arena, this required integration with the GC, so couldn't be done as an external library. Hence why a language spec was required.
[ Parent | on HN ]
Re:Major standard library changes in Go 1.20 by klodolph on Tuesday January 17, 2023 @05:44AM (#34411054)
> Why do Go enthusiasts look at types that specialize more generic data structures to ensure invariants and scoff?

I'm sorry, I'm not really sure what difference between Buffer and byte[] in Java I'm supposed to care about, except for the details of how these objects are allocated in memory. There is not really any semantic difference between them, as far as I can tell.

Maybe I don't understand what you're saying--I'd love for you to clarify the reasons why you think Go developers are, I guess, a little bit dense, or foolish, or whatever negative adjectives you like to apply to people who use Go (you know, rather than talking about the language itself--it's always fun to make fun of people).

[ Parent | on HN ]