Linked by Thom Holwerda on Sun 22nd Jul 2007 00:33 UTC, submitted by liquidat
Permalink for comment 257205
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
More News »
Sponsored Links



Member since:
2005-07-06
Simply API must be "versioned", by extendeding existing API, not completely replacing it. This usually means that if API gets published for v2.6.x. for example, it will stay stable until 3.x or 2.7 at least.
I never said that it couldn't be changed - read what I wrote. The issue raised by some here is that if you have backwards compatibility, you magically castrate the developers from making changes and enhancements.
That's how most systems work and trust me: it's a lot better to attract developers.
I never argued against it. Again, I stress - read the WHOLE thread, don't just jump in half way through the conversation making assumptions on what I or others have said.