[web2py] Re: Great summary of web2py
I think that there on the features list, frameworks seekers would love to hear about the amazing web2py ajax and component functions and all the eco method as part of the awesome mvc system. On Wednesday, March 5, 2014 6:23:14 PM UTC+2, Jorge Pereira wrote: > > VP writes: > > > > > > > > > > Specifically, to attract newbies, I would recommend making Chapter 3 > > of the book to be better than it currently is. Right now, it's very > > good. But I think there are places that can be improved. This > > chapter is where web2py can be/should be showcased to attract the > > newbies. This comes from my experience when I first learned about > > web2py. > > > > > > > I agree with VP about making chapter 3 and the rest of the book better > than > it is now, I'm learning Python and Web2Py coming from PHP/Symfony2... I > would recomend taking a look at Symfony's 2 documentantion its well > organized and looks great for programmers like me who want to learn a new > language and framework. > > Greetings to everybody. > > -- 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/groups/opt_out.
[web2py] Re: Great summary of web2py
VP writes: > > > > Specifically, to attract newbies, I would recommend making Chapter 3 > of the book to be better than it currently is. Right now, it's very > good. But I think there are places that can be improved. This > chapter is where web2py can be/should be showcased to attract the > newbies. This comes from my experience when I first learned about > web2py. > > I agree with VP about making chapter 3 and the rest of the book better than it is now, I'm learning Python and Web2Py coming from PHP/Symfony2... I would recomend taking a look at Symfony's 2 documentantion its well organized and looks great for programmers like me who want to learn a new language and framework. Greetings to everybody. -- 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/groups/opt_out.
[web2py] Re: Great summary of web2py
Yes Michele, +1 to web pages! I often see frameworks being compared in threaded discussions. That's such a waste of time when a simple reference to a webpage could tell a much better and more complete story. It is a shame that when some newbie enters a search like 'web2py vs django|flask|rails' they might so easily find some long argumentative thread peppered with expletives with someone unfairly ranting about something Massimo said in 2007. This was certainly my initial experience and I can say it was quite off-putting. We could then collectively always reference these pages in other threads. The backlinks would really boost the SEO and the inevitable scrutiny of devotees of other frameworks would help us keep the pages accurate and fair. -David On Dec 23, 11:55 pm, Michele Comitini wrote: > Maybe we should keep a comparison just on web2py.com. Pay attention > to framework lists around and putting a sane description there. > It is useless and even counterproductive starting flame wars in > threaded discussions. It is more importante that googlers find web2py > when > they search a good framework to work with. > > 2010/12/24 JmiXIII : > > > Just to give a pleased newbie feed-back : > > > _I'm newbie to web2py (well a couple of month) > > _I've never studied informatics nor did I have an informatic job > > > BUT I needed something to handle database easely + human interface + > > network for my job > > I tried a crack access => beurk => begin to learn python > > I tried Zope/Plone => too heavy > > I tried Django => not enough efficient for what I wanted > > > THEN > > I've seen some comparaison made by Massimo between Django and web2py > > 'do not remember the url) > > AND This is these comparisons which decided me to try web2py > > I'm very pleased because it is so efficient > > > you are right VP , it's a waste of time to fuel the fire. But a short > > comparison would help newbies to make their choice and choose to try > > web2py. Yet I'm speaking of comparison showing the efficientness of > > web2py not long long debates/war. > > > On 23 déc, 23:51, VP wrote: > >> On Dec 23, 3:44 am, Branko Vukelić wrote: > > >> > Or am I missing something? > > >> > In the summary, also no mention of Django or Flask. > > >> My comment is not just about that specific thread of discussion, but > >> about a general PR strategy of web2py. My suggestion to Massimo > >> still stands. Forget about Flask and Django !!! Don't talk about > >> them at all. None. Nothing. > > >> People who think that Django/Flask are superior to web2py, and/or > >> web2py is deeply flawed, aren't changing their minds. There's no > >> point to debate, justify, etc. > > >> I do not see much benefit for web2py when Massimo discusses Django/ > >> Flask. On the other hand, the (serious) newbies will get lost in hot > >> exchanges between the web2py folks and the Django/Flask folks. > >> Occasionally, this dude Armin will come around the proclaim web2py to > >> be the worst thing there is. And my suggestion to Massimo is that he > >> will have to live with that, and instead of spending energy to justify > >> him, turn that energy into making web2py to be a great platform. > > >> Specifically, to attract newbies, I would recommend making Chapter 3 > >> of the book to be better than it currently is. Right now, it's very > >> good. But I think there are places that can be improved. This > >> chapter is where web2py can be/should be showcased to attract the > >> newbies. This comes from my experience when I first learned about > >> web2py. > >
Re: [web2py] Re: Great summary of web2py
Maybe we should keep a comparison just on web2py.com. Pay attention to framework lists around and putting a sane description there. It is useless and even counterproductive starting flame wars in threaded discussions. It is more importante that googlers find web2py when they search a good framework to work with. 2010/12/24 JmiXIII : > Just to give a pleased newbie feed-back : > > _I'm newbie to web2py (well a couple of month) > _I've never studied informatics nor did I have an informatic job > > BUT I needed something to handle database easely + human interface + > network for my job > I tried a crack access => beurk => begin to learn python > I tried Zope/Plone => too heavy > I tried Django => not enough efficient for what I wanted > > THEN > I've seen some comparaison made by Massimo between Django and web2py > 'do not remember the url) > AND This is these comparisons which decided me to try web2py > I'm very pleased because it is so efficient > > you are right VP , it's a waste of time to fuel the fire. But a short > comparison would help newbies to make their choice and choose to try > web2py. Yet I'm speaking of comparison showing the efficientness of > web2py not long long debates/war. > > > > On 23 déc, 23:51, VP wrote: >> On Dec 23, 3:44 am, Branko Vukelić wrote: >> >> > Or am I missing something? >> >> > In the summary, also no mention of Django or Flask. >> >> My comment is not just about that specific thread of discussion, but >> about a general PR strategy of web2py. My suggestion to Massimo >> still stands. Forget about Flask and Django !!! Don't talk about >> them at all. None. Nothing. >> >> People who think that Django/Flask are superior to web2py, and/or >> web2py is deeply flawed, aren't changing their minds. There's no >> point to debate, justify, etc. >> >> I do not see much benefit for web2py when Massimo discusses Django/ >> Flask. On the other hand, the (serious) newbies will get lost in hot >> exchanges between the web2py folks and the Django/Flask folks. >> Occasionally, this dude Armin will come around the proclaim web2py to >> be the worst thing there is. And my suggestion to Massimo is that he >> will have to live with that, and instead of spending energy to justify >> him, turn that energy into making web2py to be a great platform. >> >> Specifically, to attract newbies, I would recommend making Chapter 3 >> of the book to be better than it currently is. Right now, it's very >> good. But I think there are places that can be improved. This >> chapter is where web2py can be/should be showcased to attract the >> newbies. This comes from my experience when I first learned about >> web2py.
[web2py] Re: Great summary of web2py
Just to give a pleased newbie feed-back : _I'm newbie to web2py (well a couple of month) _I've never studied informatics nor did I have an informatic job BUT I needed something to handle database easely + human interface + network for my job I tried a crack access => beurk => begin to learn python I tried Zope/Plone => too heavy I tried Django => not enough efficient for what I wanted THEN I've seen some comparaison made by Massimo between Django and web2py 'do not remember the url) AND This is these comparisons which decided me to try web2py I'm very pleased because it is so efficient you are right VP , it's a waste of time to fuel the fire. But a short comparison would help newbies to make their choice and choose to try web2py. Yet I'm speaking of comparison showing the efficientness of web2py not long long debates/war. On 23 déc, 23:51, VP wrote: > On Dec 23, 3:44 am, Branko Vukelić wrote: > > > Or am I missing something? > > > In the summary, also no mention of Django or Flask. > > My comment is not just about that specific thread of discussion, but > about a general PR strategy of web2py. My suggestion to Massimo > still stands. Forget about Flask and Django !!! Don't talk about > them at all. None. Nothing. > > People who think that Django/Flask are superior to web2py, and/or > web2py is deeply flawed, aren't changing their minds. There's no > point to debate, justify, etc. > > I do not see much benefit for web2py when Massimo discusses Django/ > Flask. On the other hand, the (serious) newbies will get lost in hot > exchanges between the web2py folks and the Django/Flask folks. > Occasionally, this dude Armin will come around the proclaim web2py to > be the worst thing there is. And my suggestion to Massimo is that he > will have to live with that, and instead of spending energy to justify > him, turn that energy into making web2py to be a great platform. > > Specifically, to attract newbies, I would recommend making Chapter 3 > of the book to be better than it currently is. Right now, it's very > good. But I think there are places that can be improved. This > chapter is where web2py can be/should be showcased to attract the > newbies. This comes from my experience when I first learned about > web2py.
[web2py] Re: Great summary of web2py
Flask is nice and I am not complaining about it. Yet, if I needed something small where web2py was too much overhead (and it can be I guess), I would go with bottle.py+dal.py. The bottle source code is beautiful and the routing mechanism seems similar to flask. Massimo On Dec 23, 5:12 pm, Branko Vukelić wrote: > 2010/12/23 VP : > > > People who think that Django/Flask are superior to web2py, and/or > > web2py is deeply flawed, aren't changing their minds. There's no > > point to debate, justify, etc. > > True. > > > > I've recently tested Flask briefly. I didn't like it's way of routing. > But then I realized something (and Flask docs confirm that as well). > Flask and web2py are not even in the same league. Flask was developed > to handle small stuff, where having routing stuff dispersed around the > code base is acceptable, because the codebase itself tends to be small > in such projects. But that sucks for larger projects. In contrast, > web2py is geared towards far more organized code, and therefore larger > projects. At least to some extent. I'm not sure about globals, but I > don't develop large projects myself, so it's fine for me. > > So I don't even understand how Flask can be compared to web2py at all. > Two different things, with two different design goals. > > > > -- > Branko Vukelic > > stu...@brankovukelic.comhttp://www.brankovukelic.com/
Re: [web2py] Re: Great summary of web2py
2010/12/23 VP : > People who think that Django/Flask are superior to web2py, and/or > web2py is deeply flawed, aren't changing their minds. There's no > point to debate, justify, etc. True. I've recently tested Flask briefly. I didn't like it's way of routing. But then I realized something (and Flask docs confirm that as well). Flask and web2py are not even in the same league. Flask was developed to handle small stuff, where having routing stuff dispersed around the code base is acceptable, because the codebase itself tends to be small in such projects. But that sucks for larger projects. In contrast, web2py is geared towards far more organized code, and therefore larger projects. At least to some extent. I'm not sure about globals, but I don't develop large projects myself, so it's fine for me. So I don't even understand how Flask can be compared to web2py at all. Two different things, with two different design goals. -- Branko Vukelic stu...@brankovukelic.com http://www.brankovukelic.com/
[web2py] Re: Great summary of web2py
On Dec 23, 3:44 am, Branko Vukelić wrote: > Or am I missing something? > > In the summary, also no mention of Django or Flask. > My comment is not just about that specific thread of discussion, but about a general PR strategy of web2py. My suggestion to Massimo still stands. Forget about Flask and Django !!! Don't talk about them at all. None. Nothing. People who think that Django/Flask are superior to web2py, and/or web2py is deeply flawed, aren't changing their minds. There's no point to debate, justify, etc. I do not see much benefit for web2py when Massimo discusses Django/ Flask. On the other hand, the (serious) newbies will get lost in hot exchanges between the web2py folks and the Django/Flask folks. Occasionally, this dude Armin will come around the proclaim web2py to be the worst thing there is. And my suggestion to Massimo is that he will have to live with that, and instead of spending energy to justify him, turn that energy into making web2py to be a great platform. Specifically, to attract newbies, I would recommend making Chapter 3 of the book to be better than it currently is. Right now, it's very good. But I think there are places that can be improved. This chapter is where web2py can be/should be showcased to attract the newbies. This comes from my experience when I first learned about web2py.
Re: [web2py] Re: Great summary of web2py
On Thu, Dec 23, 2010 at 4:16 AM, VP wrote: > I've supported web2py for a long time. But I think it's time to > rethink about PR. Frankly, I think this Flask/Django business is a > distraction. I think Massimo should completely ignore and do not say > anything about Flask or Django. Where did THIS come from? Django is mentioned once by an asker "Is this a good framework to start with? Was looking at web.py, but this looks more complex yet not as django does.", and once in a response "Web2py is much easier to learn than Django and offers much more productivity than web.py.". Flask isn't mentioned at all. Or am I missing something? In the summary, also no mention of Django or Flask. -- Branko Vukelic stu...@brankovukelic.com http://www.brankovukelic.com/
[web2py] Re: Great summary of web2py
On Dec 23, 8:55 am, mdipierro wrote: > +1 > > I think we should go after PHP, ASP, JSP I think you shouldn't care. Just inject as much quality into web2py as possible, don't worry about the competition. I would actually prefer that the hordes of PHP, ASP and JSP developers not join my beloved web2py, thank you very much :)
[web2py] Re: Great summary of web2py
+1 I think we should go after PHP, ASP, JSP On Dec 22, 9:16 pm, VP wrote: > I've supported web2py for a long time. But I think it's time to > rethink about PR. Frankly, I think this Flask/Django business is a > distraction. I think Massimo should completely ignore and do not say > anything about Flask or Django.
[web2py] Re: Great summary of web2py
I've supported web2py for a long time. But I think it's time to rethink about PR. Frankly, I think this Flask/Django business is a distraction. I think Massimo should completely ignore and do not say anything about Flask or Django.
