Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The title of Go's GC announcement is "Go GC: Prioritizing low latency and simplicity", and I think that a variation of that would be a better title for this. Some users may prefer a different tradeoff, and I think it's important to know that there is a tradeoff. But as this article says "I have no doubt that many Go users are very happy with the new runtime.", and that seems like a worthwhile metric.

https://blog.golang.org/go15gc



That there are tradeoffs is the whole point, the messaging makes it sound like there aren't.


The title says "prioritizing"; if that's not synonymous with "making tradeoffs", I don't know what is.


> But as this article says "I have no doubt that many Go users are very happy with the new runtime.", and that seems like a worthwhile metric.

A metric for what? For it making many Go users very happy, or for making rather big claims like "future of GC"?


Making your users happy seems like a reasonable goal. Neither the article nor the Go announcement suggest this is the "future of GC".


First line of the Go announcement: "Go is building a garbage collector (GC) not only for 2015 but for 2025 and beyond"

to me, that suggests they think they have the future of GC


I thought it was implied that they were talking about a GC for Go specifically.


There is a difference between "a future-proof GC" and "the future of GC".




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: