4 ms·
Not OP but yep. Forced SDK upgrade, dependency chain and vendor driven churn. But, eg, Twilio been using the same HTTP methods for like 10 years. Many other S
by edoceo 2y ago
Not OP but yep. Forced SDK upgrade, dependency chain and vendor driven churn.
But, eg, Twilio been using the same HTTP methods for like 10 years. Many other SDK based interfaces (not necessarily Stripe) have forced that churn.
- noitpmeder 2y agoTrying to understand, wouldn't you see the same issues if you depended on an API that had a breaking change? I guess my view is that shitty interfaces are shitty and people don't think enough about forwards/backwards compatibility, but it's not tied to a pure SDK or API problem
- csomar 2y agoMost serious enterprises should have their API versioned.
- MarcelOlsz 2y agoIt adds an extra layer of maintenance. Instead of a breaking API change now you might also have an SDK that hasn't updated yet or is incompatible for any number of reasons, and you don't want to be embedded in it before you find out. It's just easier using a REST API.