«

Firstly, this topic is NOT intended for trolling or starting any flame
wars.

I want to know if anyone has experience with these frameworks, and if
so, how do they compare? Which one do you prefer?

Going back to school in a few days, I simply don't have the time to try
both.

-thanks
http://djangoproject.com
http://rubyonrails.com

flamesrock wrote:
> Firstly, this topic is NOT intended for trolling or starting any flame
> wars.

Whatever you say, "flamesrock".

http://griddlenoise.blogspot.com/200...off-rails.html
http://www.boddie.org.uk/python/web_frameworks.html

flamesrock wrote:
> Firstly, this topic is NOT intended for trolling or starting any flame
> wars.
>

Thanks for the links, gene tani.

D H,
'flamesrock' refers to the Calgary Flames, not the act of flaming.

gene tani wrote:
> http://griddlenoise.blogspot.com/200...off-rails.html

I don't think that opinion is very founded - especially what he thinks
metaprogramming is about, and what not.

What he seems not to grasp is the crucial difference between django and
rails/subway (at least in the way the yare _used_ by his examples):

- rails/subway reflect over a existing table. They create OR-mappings
based on that. You only specify exceptional attributes for these mappings.

- django specifies the whole meta-model in python - and _generates_
the SQL/DDL to populate the DB. So obviously you have to be more verbose
- otherwiese you won't have the fields you need.


I personally prefer the latter approach - I want my tables modeled after
my objects, not the other way round. I tried to find out if subway and
rails can do the same - that is, generate the sql. For subway the lack
of documentation prevented that, and I didn't find it in rails , too.

And there is at least one shortcoming to the first approach, when using
the most popular RDBMS, MySQL: The lack of foreign key constraints makes
me wonder how to automatically infer 1:n or m:n relationships. From a
rails tutorial, I see that one has to declare these too:

http://www.onlamp.com/pub/a/onlamp/2...ls.html?page=5


But maybe someone who has expirience with subway or rails can elaborate
on this?

Diez

Here's another, (i'm just flipping thru del.icio.us and furl tags, not
endorsing any viewpoints. I've never looked at Django or Subway, but I
do need to look at zope 3, i think):

http://www.magpiebrain.com/archives/...ils_and_django

Diez B. Roggisch wrote:
> gene tani wrote:
> > http://griddlenoise.blogspot.com/200...off-rails.html
>

Dnia 5 Sep 2005 19:06:51 -0700, flamesrock napisa³(a):

> Firstly, this topic is NOT intended for trolling or starting any flame
> wars.
>
> I want to know if anyone has experience with these frameworks, and if
> so, how do they compare? Which one do you prefer?

Django's ORM does not work with SQL Server (only Postgresql, MySQL and
SQlite). it would be problem to use Django for m$ based intranets. Rails
has more features, better docs and seems to be more mature than Django. And
last but not least, Django has no official release up today.

--
JZ

flamesrock wrote:
> D H,
> 'flamesrock' refers to the Calgary Flames, not the act of flaming.
>

It was just a joke about your statement and your name. I thought it was
obvious enough that a smiley wasn't necessary. I don't care though,
flames happen on comp.lang.python all the time.
Go with Rails. Django is only like a month old. Unless you are more
comfortable using python than ruby.

D H wrote:

(snip)
> Go with Rails. Django is only like a month old.

Please take time to read the project's page. Django has in fact three
years of existence and is already used on production websites, so it's
far from pre-alpha/planning stage.

--
bruno desthuilliers
python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for
p in ''.split('@')])"

bruno modulix wrote:
> D H wrote:
>
> (snip)
>
>>Go with Rails. Django is only like a month old.
>
>
> Please take time to read the project's page. Django has in fact three
> years of existence and is already used on production websites, so it's
> far from pre-alpha/planning stage.
>

Don't make any assumptions about what I have and haven't read. Django
was only publicly released in mid-July. Less than two months ago.
I never implied it was "pre-alpha" or in a "planning" stage.
The Ruby framework is also more mature and much much more tested than
Django. But even then I am not stating one is inherently better than
the other. Both seem very well designed. But if you have no clue about
either project like the original poster, then I'd recommend Rails,
unless you are already comfortable with Python (and not used to Ruby),
which case go with Django.