I heard about it. It's a web framework in python with similar aims to ROR (that is, provide a full stack to create a dynamic web application), with some differences:
1. they have an admin tool to manage the app
2. the pieces of the stack (persistency, rendering, etc.) are pluggable
3. it is geared more towards creating portals than web applications.
It was created to host a newspaper social portal (don't remember the name) after the developers were fed up with php.
I didn't like it... But I think it's mostly because I don't like python...
Anyway, If you must sink you head into "yet another smart-ass ajax framework":
1. This online book might help
2. Don't worry! There are tons of example for django (including integration with other sticky, smelly, just-leave-us-alone-already, ajax frameworks like dojo, extjs, prototype, etc. also comet and rest, and of-course having everything run on jaxer and screaming my french neighbour's name at 03:40 am while running half naked on allenby street).
the paradox is - being a framework that repeats other frameworks... :o)
I didn't look for any (comparison). For me the choice is simple - RoR!
Not because I'll get the job done quicker with Ruby... Python will do just as well...
It's the "enjoying development" part the bought me (+ I think RoR has better IDE support)
you might be interested in taking a look at merb. it is more pluggable and less magic. with RoR many complaints are that you get a monolithic framework that is hard to understand because of all the alias magic that they do.
this is only said by those who didn't bother to learn Ruby/Rails thoroughly.
this can be said on any modern framework... they do lots of stuff behind. once you take the time and learn them - no magic.
i know it. and for me it's just another framework... a springweb mvc like...
at the end of the day i still find myself bothered with other issues like - why can't ActiveRecords loose the inheritance requirement, or why web pages look like 1998 jsp...
Comments
I heard about it. It's a web framework in python with similar aims to ROR (that is, provide a full stack to create a dynamic web application), with some differences:
1. they have an admin tool to manage the app
2. the pieces of the stack (persistency, rendering, etc.) are pluggable
3. it is geared more towards creating portals than web applications.
It was created to host a newspaper social portal (don't remember the name) after the developers were fed up with php.
see this video http://video.google.com/videoplay?docid=2939556954580527226 if you're interested to see the lead developers of ROR and django talk about their frameworks and debate
I didn't like it... But I think it's mostly because I don't like python...
Anyway, If you must sink you head into "yet another smart-ass ajax framework":
1. This online book might help
2. Don't worry! There are tons of example for django (including integration with other sticky, smelly, just-leave-us-alone-already, ajax frameworks like dojo, extjs, prototype, etc. also comet and rest, and of-course having everything run on jaxer and screaming my french neighbour's name at 03:40 am while running half naked on allenby street).
so exciting...
btw
their claim of being a dry framework is a kind of paradox...
don't you think?
can you explain the pardox, meaning the clone of templates ?
BTW, did you find any comparison to RoR ?
the paradox is - being a framework that repeats other frameworks... :o)
I didn't look for any (comparison). For me the choice is simple - RoR!
Not because I'll get the job done quicker with Ruby... Python will do just as well...
It's the "enjoying development" part the bought me (+ I think RoR has better IDE support)
you might be interested in taking a look at merb. it is more pluggable and less magic. with RoR many complaints are that you get a monolithic framework that is hard to understand because of all the alias magic that they do.
this is only said by those who didn't bother to learn Ruby/Rails thoroughly.
this can be said on any modern framework... they do lots of stuff behind. once you take the time and learn them - no magic.
btw - merb.
i know it. and for me it's just another framework... a springweb mvc like...
at the end of the day i still find myself bothered with other issues like - why can't ActiveRecords loose the inheritance requirement, or why web pages look like 1998 jsp...