From: Giles Bowkett <gilesb@...>
Date: 2006-10-09T07:52:49+09:00
Subject: Re: Ruby vs. Rails

I've seen "Snakes and Rubies" -- I got the impression that they didn't
really have people working on that stuff who knew the frameworks that
well. That's the problem, actually; there are so many languages that
even finding someone who could speak in detail on Django, Turbogears,
Rails, and Seaside would be unusual. This means that I'll probably
have to do it myself, and that means it probably won't happen for a
long time. (I'm supposed to be working now, in fact.)

On 10/8/06, M. Edward (Ed) Borasky <znmeb@cesmail.net> wrote:
> Giles Bowkett wrote:
> >> I don't know about other Python web app frameworks, but I don't think
> >> it's fair to classify Django as a "Rails clone" or "copycat". Django and
> >> Rails were developed independently more or less at the same time. And
> >> they were both abstracted from different web apps. As a consequence,
> >> there are some things that Django does well and Rails does poorly, and
> >> vice versa.
> >
> > Can you elaborate on that? Your statement about the history of Django
> > is absolutely accurate, I should have phrased the question
> > differently. For what particular sort of problems would you recommend
> > Django over Rails?
> >
>
> Well, I would favor Rails for applications like BaseCamp and Django for
> applications like running a newspaper web site. :)
>
> But seriously, folks, I don't know enough about Django to be able to
> prefer it for anything -- I'm too far down the Ruby/Rails path and I
> know *zero* Python. There was a whole conference last year comparing the
> two frameworks, and the whole enchilada is on the web somewhere. I think
> the conclusion was that they were both good, that Django could learn
> from Rails and Rails could learn from Django, and that Rails would
> always be in Ruby and Django would always be in Python. Google for
> "Snakes and Rubies".
>
>


-- 
Giles Bowkett
http://www.gilesgoatboy.org