2016-01-15 17:29 GMT-02:00 Carlos Cesar Caballero Díaz < desarro...@spicm.cfg.sld.cu>:
> Hi, I have written about my opinion before. The backward compatibility > should never affect the system maintenance, sometimes is better just remove > the old functionalities to make way for the new ones, the backward > compatibility in the long term will become unsustainable. > > In my opinion, something like a 90% of compatibility and a good migration > guide should be enough, there are alternatives as the yii framework > migration from 1.x to 2.x, they in some way could run the two versions side > by side ( > http://www.yiiframework.com/doc-2.0/guide-tutorial-yii-integration.html#using-both-yii2-yii1 > ) > > I know that one of the main promises of web2py was the backward > compatibility, but I am sure that developers (web2py users are developers) > prefer a clean system with new useful features. > +1 -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
