Hacker News Reader

Yes, after some discussion and minor modifications (and removal of a few features): https://github.com/golang/go/discussions/47323 ... I understand the motivation for this new package, but it does seem like a large API surface to have imported into the stdlib.

View on HN

Being that this is coming from a (former) core maintainer of the stdlib I think it's worthy.

Who it came from is irrelevant

No it's not. Someone who is a former core maintainer likely has better perspective on what belongs or doesn't than 99% of the community. There's a reason most stdlib and language decisions in Go are run through an extremely small cabal of people.

I think what OP is trying to say is that the merit of a given feature alone should determine whether it goes into the stdlib or not and author's reputation should not result in something being merged that wouldn't otherwise.

Well, your sentence contains the word should two times. To me, this indicates a wish that differs from reality.

Of course it should have merit, and it does. I invoked the author's reputation in that he previously had both contributed and determined merit -- his opinion carries far more weight than any random gopher.

Isn't that one of Go's main value propositions? A batteries-and-kitchen-sink-included stdlib?

Kitchen sink seems too far. Batteries is part of it.

Reply on news.ycombinator.com