From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <5480eb5b48baf626b0c86719df8647a6@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 16 Apr 2009 14:51:35 -0400
To: 9fans@9fans.net
In-Reply-To: <9ab217670904161050y4e51be4ey7117a27985f10d93@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Rails? (was Re: web server)
Topicbox-Message-UUID: de280db4-ead4-11e9-9d60-3106f5b1d025

On Thu Apr 16 13:52:22 EDT 2009, devon.odell@gmail.com wrote:
> 2009/4/16 hiro <23hiro@googlemail.com>:
> > What is the advantage of rails anyway?
> > I had a quick glance, but still don't really understand it's function.
>
> MVC development model. Allows you to abstract the data from the code
> from the design, but easily access needed parts from other needed
> parts. One of the big things here is the ORM, which basically maps
> information in a database to native language objects.

call me ignorant, but i've always seen such a model (ha) as provable
wrong.  in fact, it seems so obviously wrong that i never thought much
about it.

without some constraints on the data, you can't show that your design
works.  without some idea of what the data could be, how do you pick
appropriate algorithms?

when i worked in the web world, i took a couple of stabs at this and
usually things would be great for a little while.  new business logic would
fit just fine and life was good.

and then two weeks later the director of marketing would be in my office
talking about his new idea.  it was uncanny how it managed to always ask
for something we just couldn't do.

- erik