VP vtp2007@... 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
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 vtp2007@... writes:
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'
On Dec 23, 8:55 am, mdipierro mdipie...@cs.depaul.edu 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
On Thu, Dec 23, 2010 at 4:16 AM, VP vtp2...@gmail.com 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.
On Dec 23, 3:44 am, Branko Vukelić stu...@brankovukelic.com 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
2010/12/23 VP vtp2...@gmail.com:
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.
Off-topic
I've recently tested Flask briefly. I didn't like it's way of routing.
But then
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
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
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
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.
+1
I think we should go after PHP, ASP, JSP
On Dec 22, 9:16 pm, VP vtp2...@gmail.com 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
12 matches
Mail list logo
