Introduction article on Ruby on Rail published

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

The Methods & Tools newsletter has just released in its html archive
section the article "An Introduction to Web Development Using the Ruby
on Rails Framework". This article presents the basic concepts used by
the popular Ruby on Rails web development framework.

Re: Introduction article on Ruby on Rail published

editormt wrote:
Quoted text here. Click to load it
Who gives a rats ass?

Re: Introduction article on Ruby on Rail published

editormt wrote:

Quoted text here. Click to load it

: > "The model in a database-driven Web application is contained in the

Only if you don't use MVC at all.  8-(   What's next, a bunch of
typical rats-ass PHP claiming to be "MVC" because it must have a
separable Model, after all it has a "database" ?

IMHE, MVC is over-rated anyway.  VC is the good stuff -- most of the
advantages come from separating these two components, the extra for
additionally separating the Model out
too offers much less payback in comparison.

I'm no fan of Ruby or Rails. IMHO it's a fine framework for
implementing trivial stuff quickly, but it runs out of steam far too
early. What you get (AFAIK) is a Model that's tightly coupled to being
a single-table CRUD interface. Now they're just _easy_, whatever you
write them in. I don't have a problem writing these, I have a problem
writing the bigger stuff.

There's also a problem that Rails' coupling between Model and
Controller is too high to really be regarded as separable. Consider
this quote:

: > "We notice here another convention: the url needs to comply with a
specific format.
: > In this case the format is
' '. "

So the feature set of Model pervades right out to the URL structure ?
That's not a convention, it's a massive design flaw!   Go look at
Struts (et al.) and see the trouble that large systems have to go to to
avoid this, and the necessity of doing so.

I've read plenty of intro-level articles on Ruby on Rails and this
isn't a bad one. They all leave me thinking that it has nothing to
offer me as a developer though (I'm writing powerful but verbose Python
instead). What I'd _really_ like to read is a Rails article called
"Beyond the CRUD - Rails Models that are more than a simple updatable
DB view".  Does Rails have anything to offer here?

PS - Thanks for posting this useful and interesting link.
Viper needs to grow up a little, maybe discover girls or smoking and
find a new hobby.

Site Timeline