On Jul 10, 9:12 am, Vinicius Assef <vinicius...@gmail.com> wrote: > Hi guys. > This message is more about policy rather than technology, ok? > > I am new to web2py and did not develop anything with it, yet. > I just read some docs, watched some slides and video tutorials. > > As as newcomer Django user too, I could see some changing behaviour > between versions before 1.0. And who can guarantee me it won't happen > after it? Nobody. I don't see some care about backward compatibility > in Django. > > What's web2py commitment with backward compatibility?
We are fully committed to backward compatiliby. We never broke it in 2 years. We do not accept patches that break it. That is one of the reason we call web2py an "Enterprise framework". I thought we said that in the main web page but somehow it disappeared in the last edit. I will put it back. > If I develop code, this code will turn into "legacy code" in the very > moment it's in production, right? > And some of the worse things on working with customers, is answering > something like: "OK, I can make the change you are asking me. But I'll > have to charge an extra bit due to 'technology update'." My customer > doesn't care about it. And he really doesn't have to. It's my > profession. Not his, right? > > Consequently, as a professional, I care about maximizing my own time > investment on learning and using languages and frameworks. > > As a mainframe professional for 21 years long, even today I am allowed > to run some programs I developed in my early days on IBM MVS operating > system (I'm talking about 1988!). With no change at all. Such > environment is very stable, despite of language evolution. Yes, > languages change there, too. But it's always backward compatible. It's > about maximizing time and money. > > Is there anywhere written about it in web2py documentation or website? > I've not found it, yet. > IMHO it's one of the most important issues when some company chooses > some technology to use. > > I am not talking about compatiblity among python versions. I know it's > not a web2py issue, but python's. I'm referring about compatibility > among web2py versions, itself. > > -- > [ ]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 web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
