On Thu, 14 Dec 2006 18:17:16 -0600
Erik Funkenbusch <erik@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> On Thu, 14 Dec 2006 13:18:22 +0000, Roy Schestowitz wrote:
>
> > Ruby on Rails is gaining momentum.
> >
> > ,----[ Quote ]
> >| Since its first release by David Heinemeier Hansson in middle 2004,
> >| Ruby on Rails has enjoyed strong positive trend both in the open
> >| source and web development community. This trend can be easily
> >| noticed in Google Trend's statistics.
> > `----
> >
> > http://www.railsonwave.it/2006/12/12/ruby-on-rails-is-gaining-momentum
>
> It's not really Ruby that's got peoples attention, it's rails in
> particular. But Rails is really only half a solution. It's great for
> people that simply don't care about the data model. They have data,
> and they want to store it in a database, but don't really care how.
>
> Most corporations, however, have very large and complex data models
> they require you to use. Ruby does nothing for this sort of
> development. Even most product oriented web applications have
> specific data models that they document and publish. Rails doesn't
> help there.
>
> Rails doesn't help when you want to create normalized data that
> doesn't duplicate data. Rails doesn't help when you want to utilize
> data from multiple, often non-heterogenous sources.
>
> It's a great tool for certain kinds of sites, but it's certainly not
> for everyone, and it's not general purpose.
no, there is no single solution that is the best for everything. except
perl that is.
rails is not restricted to just creating everything for the designer.
but it is great for getting a site up in as little work as required.
i would say it's very good for prototyping. then, once something is
proved to be working, send it it off for redesign in accordance to the
company model.
--
Regards, Ed :: http://www.bsdwarez.net
just another c++ person
When in the presence of Mr.T a magic-8-ball ALWAYS predicts PAIN!
|
|
