If you have made up your mind about using web2py and you have to go through committees to have it approved you should consider:
- print a copy of http://mdp.cti.depaul.edu/examples/static/web2py_vs_others.pdf (outdated but better than nothing) - make list of open issues and bug reports for web2py and competing frameworks - check responsiveness of mailing lists by asking web2py/dago/rails/ etc the same questions. - getting a quote for professional support time from one of the associated companies Massimo On May 12, 3:28 pm, JohnMc <maruadventu...@gmail.com> wrote: > I will give you a perspective from someone who comes from a web/php - > cakephp perspective -- > > On May 12, 4:30 am, giohappy <gioha...@gmail.com> wrote: > > > Dear web2py group, > > I'm going to adobt a python web application framework for my next > > works, and until yesterday I was oriented to Django, as it seems to > > give me the best tradoff between simplicity, rapidity, power, etc > > I initially went the route, Django, as you were considering. I was > about 1/3rd the way though a small application before I noticed a > trend. In many cases to have the behaviors I wanted from Django I was > ripping out small code segments and replacing them with others. I have > generally never experienced that level of retrofit in a framework > before. > > So I dug a little deeper and website ever website I visited I saw this > trend. One went so far as to recommend pulling out the ORM and > replacing it with another! That in my mind leads to compatibility > issues, training concerns if its a large team effort, etc. At that > point I put the cursor down and looked elsewhere. > > > A friend of mine ha suggested me to have a look at web2py, and I admit > > I've been impressed by its features.... but as always, when one has to > > choose a technology on which to invest, the diffusion and the long- > > term support are other foundamental features to evaluate it. > > So my 1 billion $ question is: the web2py community seems to be > > growing, but it's two order of magnitude smaller the django's, and the > > google group activity is considered "low" respect to the "high" > > django's group. > > Django has had a headstart for one. But I would not configure > community size alone in your decision. The more important issue is -- > do you get answers? I have not been disappointed. Its developed into a > fair team of responders. > > 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. > > 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. > > The quandary is of course how do you overcome (A) to make (B) a > reality? Whenever I have faced (A) with management a prototype usually > sells it. There is one core problem that management wishes solved. > Write a Web2Py controller(s) for it, put a simple pretty face on it > and take that into the proposal meeting. The fact that they see the > problem almost resolved overcomes (A) and issues about what it was > written on is forgotten before the meeting is adjourned. (It also > eliminates your doubt it can be done, as you just did it.) > > Long term investment. Is that in reference to your time/career or the > projects? For a project, I am surprised if a program lasts 5 years > these days. That is how fast both technology and business processes > change. Yourself. Its well worth the effort. > > Any issues? minor -- > > * Documentation. Documentation is very complete but somewhat > dispersed. The Manual and the AlterEgo docs are both must reads. There > are also very good example techniques in the Rolling with Web2Py pdf. > Contributors are working on documenting internals that when complete > will answer a lot of questions. (At least for me.) > * Helper tools. Web2Py has tools they are just not as extensive as was > is available to Django, as yet. Django just started sooner. > > > > > thanks a lot to everyone, and my complments for this great work! > > giovanni > > Web2Py has been a good choice for me. I have completed 3 projects to > date and am on my 4th. It has not let me down. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
