API Stability Issues
The cluster revolves around debates on the risks of unstable APIs that change frequently, breaking third-party code and integrations, and whether providers should prioritize stability or rapid iteration.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Well, they should have an API, then it wouldn't matter. Until they changed the API.
Of course it could have! No API is foolproof
Wouldnt the only solution to "see if you code worked with changing apis" to either1) never change apis even if you were wrong or you have more opportunities or 2) know everything beforehand and implement the api perfect
In all likelihood, they wanted to be able to change the API as they see fit, and didn't want to have other people depending on an API that was changing rapidly. Can't fault them for that.
People might not care, but APIs do.
And change the api the next day destroying all work done by said developers.
and they would break their API again
I now have a lot to deal with API which was created by people sharing your view. It is a nightmare.
This. The API and its feature set is liable to change. This isn't a broken promise because no promises were made.
Why is it a problem to use an API?