The problem with Web2Py is that it does not have a niche. Right now, Django is occupying the same niche. As the first-comer, it has the advantage that people already know how to use it. Until Web2Py manages to have a benefit greater than its own learning curve, Web2Py will continue to sit in second place.
I hereby invoke the Jack Welch rule - Be first or second in any endeavor, otherwise get out. Were Web2Py to be number two behind Django after a concerted effort, that quite frankly would be an outcome worth crowing about. Being number two in the software game is not a bad place to be. I have said in a previous post that Web2Py support of a schemeless DB would put it in a position to have a niche. The 'cloud' might have a lot of action but there is still going to be whole swaths of the economy where the cloud will not be feasible (eg. NYSE). Which DB I leave up to those more insightful than myself. JohnMc On Jul 17, 2:34 am, Bottiger <[email protected]> wrote: > > Finally, this community has to do a better job at outreach. You should > > talk to your friends and blog about web2py. You must talk about the > applications you build with it. We do not lack developers. We lack > salesmen. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
