5 ms·
Is this Tailscale’s library imported into Go’s stdlib?
by lifty 5y ago
Is this Tailscale’s library imported into Go’s stdlib?
- pphysch 5y agoYep
- benhoyt 5y agoYes, after some discussion and minor modifications (and removal of a few features): https://github.com/golang/go/discussions/47323 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.
- na85 5y agoIsn't that one of Go's main value propositions? A batteries-and-kitchen-sink-included stdlib?
- philosopher1234 5y agoKitchen sink seems too far. Batteries is part of it.
- pstuart 5y agoBeing that this is coming from a (former) core maintainer of the stdlib I think it's worthy.
- kortilla 5y agoWho it came from is irrelevant
- voidfunc 5y agoNo 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.
- owaislone 5y agoI 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.
- scns 5y agoWell, your sentence contains the word should two times. To me, this indicates a wish that differs from reality.
- pstuart 5y agoOf 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.