The concepts you discuss are... one perspective, one sided (even if
important).

Backward compatibility is (in the big picture) a double-edged sword.

Yes, Massimo is dedicated to backward compatibility, but Python 3 is not.
Python not being so wed to backward compatibility has it's benefits (see
http://reinout.vanrees.org/weblog/2009/07/01/ep-bruce-eckel.html and
http://www.artima.com/weblogs/viewpost.jsp?thread=260578 for example).

Certainly, from web2py's end, backward compatibility is a goal.  How many
people still run Python 1.6 code, without having migrated it forward (can I
see a show of hands?) --- That's my point.   When Python 3 moves into the
forefront, you may need to make small changes, but this is not the kinds of
"rewrites" you are talking about, where your clients don't care.   This is
"practically backward compatible" in that nothing devastating or earth
shaking takes place.

This is probably the same approach to expect here.   Backward compatibility
is a goal... But you are not encouraged to use T2 (anymore); there are
better ways now.  Yes, it will still run.   And DAL will change, for the
better.  ... and so on.

The point is to "keep making sense" - consider the client, the developer,
AND forward progress, and strike that balance of concerns.  (That, after
all, is what intentional design is - consider the involved parties, and
balancing concerns).

- Yarko

On Fri, Jul 10, 2009 at 11:08 AM, viniciusban <[email protected]> wrote:

>
>
>
> On Jul 10, 12:29 pm, mdipierro <[email protected]> wrote:
> > OK. check out web2py.com, the second item after the slides.
>
> Nice!
> And so quick. :-)
>
> --
> [ ]s
> Vinicius Assef.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to