we could add database hooks. Would you make a wishlist for the api? On Dec 11, 12:23 pm, Thadeus Burgess <[email protected]> wrote: > Summary: > > web2py: > simple, concise forms > python as a templating language > true model controller view cycle > friendly table definitions > sql-like query functions > automatic-migrations > ...so much more > > django: > database hooks > > The details: > > Django makes no logical sense... at least to an anal programmer like me :) > > web2py makes things simple. I can accomplish the same thing, in less > lines of code, and in a more logical sense with web2py. Just take > SQLFORM for example. It's simple. It's logical. It works, especially > SQLFORM.factory. Django introduces a lot of spaghetti code by design. > I have yet to see a django form that was actually useful that wasn't > spread across a few different files. (forms.py, views.py, etc...) > > Every time I go to write a django app, it seems I cannot create a > single view without having to define my own custom templatetag to do > what I want to accomplish. This is where web2py excels in having > python as its templating language. > > The main problem I have against django is the mindset of its design. > In my opinion, its logically backwards, its archaic, its spaghetti > string. This comes from the design being centred around the newsroom. > Django (in my opinion) breaks logical engineering standards. MCV > (web2py) vs MVT (django). Not that this effects how django performs, > but it hurts my brain. Web2py, doesn't hurt my brain. > > I also hate hate hate hate the way django defines models and queries. > Again it just seems like, it's trying too hard. I love in web2py that > you just define your fields, and in one string say what type it is, > and have that translated to your database. Also, queries, what is > django thinking? Why does the query have to be hidden behind an > archaic ill-logical double underscore syntax? I love that web2py's > queries are close to SQL, those SQL classes I took in college actually > mean something. Django queries, by design, make you think as a > non-programmer. Lastly, you can't beat automatic migrations during > development. > > That being said, there are things about django that I like, things > that one day I hope start inching their way into web2py. I would like > to have database hooks, something that was more behind the scenes that > .accepts(onvalidation=...).... actually that's about the only thing I > can think of django having that I wish web2py had. > > I know that many would disagree with me, especially those who use > django. It's just my opinion, and opinions are like butt holes, we all > have them, and they all stink. I do not want to start a flamewar > (which is why I kept it to a one liner in the first post), I am just > answering Yarkos question. > > -Thadeus > > On Thu, Dec 10, 2009 at 11:19 PM, Yarko Tymciurak > > <[email protected]> wrote: > > can you be more specific? What do you like more when you compare? > > > On Dec 10, 10:20 pm, Thadeus Burgess <[email protected]> wrote: > >> Everytime I look at a django app... it makes me so grateful for web2py :) > > >> -Thadeus > > > -- > > > You received this message because you are subscribed to the Google Groups > > "web2py-users" 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 > > athttp://groups.google.com/group/web2py?hl=en. > >
-- You received this message because you are subscribed to the Google Groups "web2py-users" 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.
