> 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 ther

> 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.