4 ms·
The reason I stopped integrating any API based system (FB, Twitter, etc...) into my code bases for services I don't pay for (or my customers) is because they al
by RobertRoberts 4y ago
The reason I stopped integrating any API based system (FB, Twitter, etc...) into my code bases for services I don't pay for (or my customers) is because they all changed willy-nilly and broke on a regular basis.
This is more likely to break (be broken by google) than an official API, and those are bad enough. (hard pass on even trying this out, especially if it's good/nice I'll want to use it and kick myself later for being an idiot.)
- stingraycharles 4y agoUnfortunately it’s rarely that these kind of decisions are based on technical merit, but instead because they’re part of the business proposition, or requested by other parts of the business (sales/marketing). Other than that, I fully agree that you should try to minimize your dependence on them, it’s not good a good position to be in; what’s in the best interest for YouTube today may not be the case in one year.
- cromwellian 4y agoIn my experience, private APIs are expected to be refactored, and you should not depend on them. I don't think sales/marketing are involved at all. For a public API, sure, but don't expect private, undocumented APIs not to break you, in fact, you SHOULD expect them to change, especially in any codebase that is actively being maintained.