Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sure. But are you going to choose API provider "A" with a history of keeping stable APIs working 10+ years, or API provider "B" which can and does change stuff every year? What's your expected maintenance cost over the lifetime of the service?


Fair point.

On the other hand, Google is notorious for EOLing services that don't have a billion users, even compared to other cloud/web companies. That should be priced in.


I guess it could still make sense for tech-heavy, "we rewrite 50% of our code every month"-companies, like... Google?

Maybe they're mostly running their cloud to iron out the kinks im the API's they use themselves?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: