[dasil003]

Interesting tangent to this, after doing PHP from 2000 to 2005, I hopped on the Rails bandwagon full-bore and was using it even for small clients. 6 years later I feel that it was a bit self-serving because those old Rails sites are creaky and painful to upgrade—or even to find someone else to work on—compared to my PHP sites from the same era.

Now that I have ample outlet for my creativity I can be a bit more objective and admit that as much as I love Rails, it's a terrible platform for build-it-and-forget-it. Rails shines for core business apps under continuous evolution.

[rhizome]

What do you consider to be a good "build-it-and-forget-it" platform?

[dasil003]

PHP, Java, Cobol? It's all relative I suppose.

[endtime]

You're recommending COBOL as more maintainable than Rails? I don't know Rails, but I find this very hard to believe.

[raganwald]

The times, they are a-changing. COBOL has its own agile framework:

http://www.coboloncogs.org/INDEX.HTM

[dasil003]

Where did I say maintainable? This is about stability over time.

[endtime]

>creaky and painful to upgrade—or even to find someone else to work on

What do you mean by maintenance, if not that?