4 ms·
Go developers made a reasonable choice. Unstable API is just another way to say that there is no API. And with zero API any change is compatible and cannot brea
by fpoling 8y ago
Go developers made a reasonable choice. Unstable API is just another way to say that there is no API. And with zero API any change is compatible and cannot break anything. So there is no need for v0.
- cesarb 8y agoIf there is no API, how can the library be used? Every function a library exposes is part of the library's API, so for a library to have no API, it cannot expose any function.
- deleted 8y ago[deleted]
- TheDong 8y ago> Unstable API is just another way to say that there is no API No, it doesn't mean there is no API, it means there is no compatibility promise; it means there is an API per version, and the relationship between them i s not known. > And with zero API any change is compatible and cannot break anything That would be true, but this isn't "zero API", it's "zero promise of API compatibility" That makes your statement "With zero API compatibility any change is compatible"... That's very obviously wrong. Please don't jump through these bizarre logic hoops to try and justify what go does here.