4 ms·
> If the API version he's using doesn't stop working there is no real reason why it couldn't just continue to work for a very long time That's sort of insane.
by ajross 11y ago
> If the API version he's using doesn't stop working there is no real reason why it couldn't just continue to work for a very long time
That's sort of insane. We aren't talking about a static library here. Of all the public web APIs available in 2007, how many are still alive? Maybe 5%? Less? Google Maps is one of a tiny, tiny set of still-relevant products that still support their decade-old interface.
And don't get me wrong: it's a great product. But getting back to the discussion, it's a proprietary product, and anything built on it needs to be aware of the inherent business risk if, some time over the next decade, the API provider decides to terminate support. They did.
- manigandham 11y agoYour comment didn't argue against anything the parent said. What exactly is "insane"?
- BinaryIdiot 11y ago> That's sort of insane. We aren't talking about a static library here. Of all the public web APIs available in 2007, how many are still alive? Maybe 5%? Less? Google Maps is one of a tiny, tiny set of still-relevant products that still support their decade-old interface. You never stated you were referring to ONLY public web apis. In fact you simply said "Apps". But even if you really meant only public web apis there is precedent (Google's many APIs) where APIs will continue years and sometimes even decades. Is it unlikely? Probably, depending on what you're doing, but certainly not impossible nor "insane". As a software developer who's seen web apps function for a decade + with little to no changes (one of which actually did rely on a third party API) I fail to see how anything I stated was "insane". Not everything has to have major breakages every 6 months.