Constantly changing frameworks/APIs - how do we keep up?
Posted
by Jamie Chapman
on Stack Overflow
See other posts from Stack Overflow
or by Jamie Chapman
Published on 2010-05-05T18:21:35Z
Indexed on
2010/05/05
18:38 UTC
Read the original article
Hit count: 318
This question isn't really for any specific technology but more of general developer question.
We all know from experience that things change. Frameworks evolve, new features are added and stuff gets removed.
For example, how might a product using version 1.0 of the "ABC" framework adapt when version 2.0 comes along (ABC could be .NET, Java, Cocoa, or whatever you want)?
One solution might be to make the frameworks backward compatible; so that code written for 1.0 will still work in version 2.0 of the framework.
Another might be to selectively target only version 1.0 of the framework, but this might leave many fancy new features unused (many .NET 2.0 apps seem to do this)
Any thoughts on what we as developers should do as best practice to keep our technologies up to date, whilst not breaking our applications?
© Stack Overflow or respective owner