On Tue, May 12, 2009 at 3:28 PM, JohnMc <maruadventu...@gmail.com> wrote:
...... > > What's you trend analysis? Would you suggest adopting > > web2py for a long-term investment? I ask, possibily, for an "unbiased" > > answer, as I'm going to adopt it as a backend for a public > > infrastructure backend... don't put me in a bad situation! :) > > This is a two edged sword. > > A) If you have to go before a committee to get funding to do the > project Web2Py will be a harder sell than say pitching the project to > be done in Rails or TurboGears or Django. Its a mind perception > thing. Massimo - what was that video we saw / had posted a year back where someone from NOA (?) showed simple apps and what it took to bring them up quickly? I wish we would find that, and do an update. ...and not just simple app, but a change in requirements in a bigger already existing app. (that will be a harder comparison to make fairly) I _know_ from changes to a running system during PyCon that web2py is a good choice. It would be nice to quantify (I don't care about "better than" unless it's so, but establishing the class of application that web2py is what I would like to see). > > B) When the project is done, you delivered under budget and weeks > ahead of time and the Director is pitching it in a slide deck at the > next quarterly meeting WHAT the project was done in will be the > furtherest thing from management's mind. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
