Excellent point. We don't need to criticize Django. We can compare Django and web2py side by side, and show how web2py makes the job so much easier. Which brings up another point...
One of the most common refrains I hear about Django vs something like web2py is that when you scale to really BIG applications, Django has the advantage in terms of flexibility and power (by virtue of being more "explicit"). We need to quash this notion immediately. Developers are very anal when it comes to whether a tool can be used to build on a grand scale. We need to show that web2py has no limitations in this regard. A most appropriate article, then, would be one which points to several (high profile?) enterprise examples where web2py is used to build BIG applications. I'm sick of hearing how Django was used in Disqus and Instagram and Mozilla and NY Times and Pinterest. Cheers. On Wednesday, 9 July 2014 11:53:01 UTC-4, Michele Comitini wrote: > > I agree, web2py is a "pragmatic" framework. so the best way to make it > shine is comparing how to get something done: there is not (only) > theoretical blather behind it, facts and results drive web2py from the > start. > > Usually is better avoiding critics towards others, but rather underline > the qualities of web2py. That's a fundamental salesman skill. > > > > > > > 2014-07-09 17:36 GMT+02:00 Carlos Costa <yamand...@gmail.com <javascript:> > >: > >> I agree with you Massimo, the best ones are those that built something. >> Videos like this http://vimeo.com/6782736 helped me to decide to stay >> with web2py. >> Not only that title is quite "marketish" but content is so true. >> >> >> 2014-07-09 12:28 GMT-03:00 Massimo Di Pierro <massimo....@gmail.com >> <javascript:>>: >> >> I think this would help a lot web2py. >>> >>> I can share some personal experience. In my experience the best articles >>> are those that show how to build something and focus on one feature at the >>> time. People are very religious about certain frameworks and for the >>> message to get across one really has to convince them that web2py will save >>> them time and pain. One cannot convince everybody, but one can choose a >>> target audience. >>> >>> I like comparison: this is how you do X in Django (for example) - this >>> is how you do in web2py. The reason I like them is that they talk to a >>> clear audience and users of both frameworks have something to learn from >>> each other. Mind some people are very touchy and they do not like to be >>> told that another kid has a shiner tool. >>> >>> Massimo >>> >>> >>> >>> On Wednesday, 9 July 2014 08:12:55 UTC-5, yamandu wrote: >>>> >>>> I like it. >>>> >>>> I wonder if we could do it in an organized in some way. >>>> >>>> Recently I lost to convince my boss to change everything to web2py >>>> because "there are few developers that know it". >>>> So it would be very good to have a massive community. As we will have >>>> more opportunities to work on the framework we love best. >>>> >>>> Groups like this have little exposure outside. We need something else! >>>> >>>> >>>> 2014-07-09 10:03 GMT-03:00 Philip Kilner <ph...@xfr.co.uk <javascript:> >>>> >: >>>> >>>>> Hi, >>>>> >>>>> On 09/07/14 13:31, horridohobbyist wrote: >>>>> >>>>>> Let's improve web2py's PR. A blast of articles over the next year >>>>>> could >>>>>> change the fortunes of our favourite web framework. >>>>>> >>>>>> >>>>> Good piece, great finish. >>>>> >>>>> I'll take that as a challenge, and see if I can describe my own >>>>> journey from desktop databases to web2py via Zope and Plone as succinctly! >>>>> >>>>> :-) >>>>> >>>>> >>>>> -- >>>>> >>>>> Regards, >>>>> >>>>> PhilK >>>>> >>>>> >>>>> e: ph...@xfr.co.uk <javascript:> - m: 07775 796 747 >>>>> >>>>> 'work as if you lived in the early days of a better nation' >>>>> - alasdair gray >>>>> >>>>> >>>>> -- >>>>> Resources: >>>>> - http://web2py.com >>>>> - http://web2py.com/book (Documentation) >>>>> - http://github.com/web2py/web2py (Source code) >>>>> - https://code.google.com/p/web2py/issues/list (Report Issues) >>>>> --- You received this message because you are subscribed to the Google >>>>> Groups "web2py-users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to web2py+un...@googlegroups.com <javascript:>. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>>> >>>> -- >>>> Att. >>>> >>>> Carlos J. Costa >>>> Cientista da Computação >>>> Esp. Gestão em Telecom >>>> <º))>< >>>> >>> -- >>> Resources: >>> - http://web2py.com >>> - http://web2py.com/book (Documentation) >>> - http://github.com/web2py/web2py (Source code) >>> - https://code.google.com/p/web2py/issues/list (Report Issues) >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "web2py-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to web2py+un...@googlegroups.com <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Att. >> >> Carlos J. Costa >> Cientista da Computação >> Esp. Gestão em Telecom >> <º))>< >> >> -- >> Resources: >> - http://web2py.com >> - http://web2py.com/book (Documentation) >> - http://github.com/web2py/web2py (Source code) >> - https://code.google.com/p/web2py/issues/list (Report Issues) >> --- >> You received this message because you are subscribed to the Google Groups >> "web2py-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to web2py+un...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
