Compared with PHP, I’d say that frameworks reduce the pain of
application development, but they increase the pain of deployment.
Part of the problem is choice (a bad thing, in my view) and another
part is change (again, a bad thing).
Choice is bad because it demands time for the choice. Reading
documentation, reading blogs to get real-world comments, and reading
comparisons – these all take time that would be better spent on
Change is bad because it may demand continued work on existing
applications. (That’s probably fine for developers who can then earn
part of their living by maintaining existing sites, but it’s a real
pain for academics and others who are making sites to help with other
work, not as an end in itself.)
I just got the (excellent) new Agile Web D. with Rails book,
and it’s a case in point. It says that it’s a bad idea to use fastCGI,
in contradiction to the first volume of the same book. I presume these
authors know whereof they speak, so that’s a real help to me. I can
just ignore any documentation site or blog or entry on this group,
talking about fastCGI. But the switch in advice over just a year (or
so) worries me a lot. That’s why I’m writing this.
I come, finally, to my point. It’s a question.
What is the best deployment strategy, for a new application being
created in early 2007, using pre-release RoR 1.2? (I am using OS X, in
case anyone is interested in helping me directly … but I’m really
asking the question for the benefit of a wider audience.)
Thanks for reading this long post. It’s my first on this group.
Please be gentle.