Hacker News new | past | comments | ask | show | jobs | submit login

I think that might be true in cases where you're not building on such a widely distributed and incredibly backwards-compatible / gracefully-degrading platform such as the web.



And Android for that matter. I really don't see podperson's point; what Android builds have broken backwards compatibility?


IIRC, carriers not updating their customers to the most recent Android build has been a big problem.

Not really Google's fault, but perhaps Android isn't a great example.


That causes issues for being able to use the latest features, which is somewhat of a problem, but should not affect backwards compatibility. It means you have to possibly be aware of the OS features you use in your apps, but you don't have to worry about updating them due to some API being deprecated.


It's not necessarily a question of backwards compatibility. Just being forced/pestered to update constantly is an anti-feature.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: