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

Google is throwing new API's without commitment and trying to find if one of them becomes popular. This is good way to limit the risk.

Developers wait to see if Google commits to API before fully adopting it. This is good way to limit the risk.



Don't you end up with a catch 22 where developers won't write apps against an API because it may disappear, and Google gets rid of an API because nobody is writing apps against it?


I'm pretty sure that is the point nabla9 is making.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: