>From my perspective, web2py style is very much influenced by its functional approach and the usage of functors. This gives a great amount of tools to new comers, but can be problmematic with experienced programmers that have been working with a COO (class object oriented: read java) language.
I have a bit of experience with OO (truly object oriented) languages besides python, such as lisp or scheme so I feel web2py confortable. But with java experience and being used to the define Interface, define Class, define Subclass of Class, instanciate Object and so on, I understand that it is not clear how and where you can do that. Maybe it is just a matter of documentation, a "Library Reference" distinct from a "Tutorial" ? Other python frameworks stick to COO so maybe more people feel confortable, and have a API or Library Reference? mic 2011/1/10 Anthony <[email protected]>: > On Sunday, January 9, 2011 4:49:45 PM UTC-5, pbreit wrote: >> >> For one, I don't think businesses care much about backwards compatibility. >> My experience in the enterprise was that vendors were constantly churning >> out non-backwards-compatibile updates and customers were routinely several >> versions behind. > > > Maybe they remain several versions behind because they don't want to keep > dealing with backwards-incompatible upgrades (i.e., skip a few versions and > just deal with an occasional big incompatible change). The cool thing about > web2py is you can take advantage of every new feature that comes out (every > couple weeks) without breaking your programs.
