[Rails] [ANN] MuraveyWeb -- Ruby CMS (with demo)

[gsinclai at imagineis.com]

Jeremy wrote:
> I apologize for the hasty conclusion, Gavin.  We aren't the nerviest
> bunch.  You have a valid suggestion but prefaced it with inflammatory
> commentary and delivered it with a negative tone.
>
> Typically I would respond with the constructive explanation that the
> thread deserves, but I interpreted your words as a passive-aggressive
> jab, not as constructive criticism, and hypocritically responded in
> kind.  My bad.

And I apologise for my outburst.  No grudges from this end, don't worry :)

To justify the "inflammatory" comment, though, I have visited several
websites that I know to be Rails-based, and it often happens that there's
an error of some kind (usually database-related).  Sometimes it's
transient.  I never blamed Rails for any of this; it's just an artefact of
quick implementations and/or unreliable hosting (perhaps).  It's *good* to
see so many Rails-based apps up and running so quickly, but I'd rather
comment on the error pages I see, rather than leave that observation for
people looking to kick Rails.

Anyway, I already knew most of the facts presented in this thread, but I
think more could be done, as I've outlined elsewhere.  I think the problem
with the Muravey docs page was one of static content being thwarted by
dynamic routing.  Since the author of a webapp probably knows all of the
static pages, a functional test that they are being served correctly would
help avoid that problem.  (That routing issue had especial resonance with
me, having struggled with it before.)

Database problems are obviously a different story, though.

Cheers,
Gavin