+1

Coming from PHP months ago I had never touched python or anything
python related but was drawn to it by an article on how Disqus used
python and the whole MVC concept.

Tried Django but was met with less than nice responses when asking
questions while reading their book.

Found web2py as I like to hunt for all options before choosing and
found myself well aligned with web2py philosophies.

Just to name a few:
Default sane behaviour with easy ability to override,
Simple is better than complex,
Don't Repeat Yourself,
and my most favorite feature - An effort to be a COMPLETE and fully
integrated package.  I really prefer this to the glue frameworks out
there.

The book taught me python and web2py simultaneously and inspired me to
hunt all over for as much information as possible about python as I
can find.

As far as I'm concerned, if someone chooses another framework because
it makes them feel more 1337 that their using something tougher/more
"pythonic" in their view/insert subjective term here, fine.  If their
priest.py doesn't approve it as Roberto De Ioris humorously put it
above, good.  More secret sauce for us.

Still, I will continue to tell people about this amazing tool I've
found and the wonderful community behind it and look forward to web2py
winning more awards and accolades from the world over.

Congrats Massimo, contributors, and community.  Whether directly or
indirectly, you have all impacted my life for the better and I thank
you all for it.

David



On Oct 5, 8:37 pm, horridohobbyist <horrido.hobb...@gmail.com> wrote:
> I like web2py. I think it's the best web framework out there...
>
> Let me explain where I'm coming from. My first experience as a web
> developer was with Smalltalk/Seaside in 2007. It came highly
> recommended to me by a friend. He told me that Seaside was very
> powerful, very flexible, and most importantly, really easy to learn. I
> value productivity and ease of use above all else when it comes to
> software development. I don't care about ideology or the ultimate in
> power and performance.
>
> My Seaside project was completed in record time. I was a happy camper.
>
> My attitude is definitely "non-geek-like". I am not a geek. I only
> care about getting the job done in the shortest time, with the least
> effort and the least pain. This has been my guiding principle over a
> 20-year career in IT (ranging from Fortran to C, from mainframe to
> PC).
>
> A year ago, I took a whack at Django, but I did not like it. I also
> tried Java-based Wicket. But neither passed the acid test of being
> really easy to learn and use.
>
> When I came across web2py a couple of months ago, I was utterly
> astonished. For a newbie, it's fall-off-the-log easy to pick up.
> That's important to me. And being easy to use doesn't mean that it's
> lacking in power. I can be phenomenally productive with web2py.
>
> My conclusion is that web2py is actually easier than Seaside
> (heresy!). It's also easier than Django, and it's definitely much
> easier than Wicket. I can't understand why programmers don't want the
> easiest tools. I prefer to enjoy my life, take it easy, rather than
> expose myself to aggravation and headache, regardless of how much
> power you gain.
>
> But that's just me.
>
> Richard
>
> On Oct 5, 10:07 am, Farsheed Ashouri <farsheed.asho...@gmail.com>
> wrote:
>
> > i bet they event didn't create a simple site with Web2py. Don't trust them.
> > Just for test, use Django for a week and you'll be back to Web2py soon than
> > we expected and with headaches!!
> > Every day, I am creating a new website for my clients. When I was using
> > Django, just initial setup took me hours. I am not saying other frameworks
> > are not smart. Web2Py is just better.
>
>

Reply via email to