[ciapug] anit-rails article

[Matthew Nuzum]

On 9/24/07, David Champion <dchampion at visionary.com> wrote:
> He has some valid points... Personally I've avoided the big framework
> things because of some of the reasons he points out. You gain some
> benefits, but have to adapt your project to work within the framework,
> or have to hack the framework to make it work for your scope.

Wow, awesome write up. I bought an RoR book last week and am reading
through it... its nice because it spends the first three chapters
teaching Ruby and making no assumptions (I'll bring it to the PUG
meeting).

The only point I want to pick at is #3, which is the proverbial
"framework, yeah or neigh?" question.

He's basically decided he wants to write all his code from scratch.
Fine. For big projects it might make sense to write your own
framework. However, by investing the time to learn a framework and
then tailoring your application to exploit the strengths of that
framework (which is easier to do the smaller your project is) you can
experience a big boost in productivity.

There was a time that I wrote all my JS from scratch. Now I've learned
some JS frameworks. Yes, maybe 4k of custom js is now a 11k library,
but I can get my work done in 1/4th the time (or better, since cross
browser support is in the box). Totally worth it.

There are good reasons to use a framework. However, that has to be
decided after careful consideration.

I look forward to learning about the various frameworks we're evaluating.

-- 
Matthew Nuzum
newz2000 on freenode