Backward compatibility does not mean "forever" it means that we will not break it in small steps. We will break in one big step by releasing a new product, when/if there will a need for it. Like move to 3.x in 2-3 years time. When that happens we will replace the form system with a better one if a better one has been developed by then.
On Mar 19, 3:24 pm, stefaan <[email protected]> wrote: > > I've just got to read that the yii framework folks share the same > > oppinion as me about backward compatibility and the payoff to mantain it > > for ever. > > Of course everyone is entitled to his/her own opinion, but I would > like to point out that > while maintaining backward compatibility in the long run can lead to > some suboptimal code, > not maintaining backward compatibility in my experience causes > considerable additional > stress for developers using your framework. > > Keeping backward compatiblity ensures that your users can upgrade > to the newest version at any time, without fearing the extra time and > effort needed to port to a new software architecture. > Everyone that at some point started to use the framework therefore can > keep benefiting from the latest and greatest features and fixes. > The framework for your web application basically never becomes > outdated/deprecated/... Support for it never has to be gradually > phased out, > leaving the early users in agony... -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
