Welcome to WebmasterWorld Guest from

Forum Moderators: phranque

Message Too Old, No Replies

Ruby On Rails

What are the downsides for high-end or high traffic development?

4:30 pm on Apr 6, 2006 (gmt 0)

Junior Member

10+ Year Member

joined:Jan 27, 2006
votes: 0

We've been using ColdFusion here in our office for the past 4-5 years. CF is a great, easy to understand language. Even I understand the basics of it. My main programmer was a former teacher who taught herself how to use it, and ended up building an excellent and complex CMS for our web based publishing needs.

We're looking to the future, to build more interactive apps - "Web 2.0 stuff" - into future projects. I've done a quick scan of the intro to Ruby, and it really does look like a fast platform to develop on.

But what I'm wondering is what are the hidden downsides? For example ColdFusion servers are costly and ColdFusion servers (esp. shared) go down/crash/lag far more often than other servers. One thing I know for certain is that if we built a big app in CF, we'd have to have a lot of servers, and watch them all the time. It doesn't seem very appealing.

I see that Ruby and Ajax... well, they seem to go together well, from what I glean, and that could be useful in the future.

Sorry to be such a n00b about this; there's a lot of good noise about Ruby but finding people talking about the downsides is difficult.