3 ms·
I'd rather deal with that than the team at Google who maintains the grpc Go library who are more than fine breaking the public API in minor changes. https://gi
by sethammons 4y ago
I'd rather deal with that than the team at Google who maintains the grpc Go library who are more than fine breaking the public API in minor changes.
https://github.com/grpc/grpc-go/issues/3798 https://github.com/grpc/grpc-go/issues/3798
- tqkxzugoaupvwqr 4y agoIf you read the first comment, you’ll see the API was documented as being experimental. https://github.com/grpc/grpc-go/issues/3798#issuecomment-670108443 https://github.com/grpc/grpc-go/issues/3798#issuecomment-670...
- sethammons 4y agoI'm clearly in the camp of "you can add and depreciate (experimental) features all you like in minor versions, but you should only remove them in major versions" camp. See the discussion on semver and experiments: https://github.com/semver/semver/issues/238 https://github.com/semver/semver/issues/238
- dtech 4y agoThat's the rule for normal features, that would mean there is no meaningful difference between stable and experimental parts of an API.
- vlovich123 4y agoHyrum’s law. Rust mostly gets around this by requiring you run the nightly compiler and library in addition to explicitly opting into experimental pieces.