Programming Forums > Script Programming > Ruby

mongeau · Apr 7th, 2006, 2:48 PM

Here is an interesting blog post objectively evaluating why Ruby on Rails won't make it to the mainstream industry. He explains that despite its technical excellence, it's only a technology experts know about, and few businesses will be willing to make the jump. The author also makes some truly valid comments regarding the usage of IDE's -- sort of going hand-in-hand regarding this recent forum topic.

Jessehk · Apr 7th, 2006, 5:18 PM

To me, Ruby is an amazing language. Not suited to everything, but what it does, it does amazingly well. Not having done any web development, I cannot comment on RoR.

At the same time, I think the author makes very valid points. It has been demonstrated in the past that features and quality do not always determine popularity.

SirBob1701 · May 29th, 2006, 10:53 PM

Before I reply I must state that I am just now learnin Ruby on Rails. I have taken an internship at a small corperation and am developing some webased tools for them to track various aspects. I had read that Ruby on Rails was suppose to make the task quick and easy but I find there are no really indepth tutorials for Large relational databases where you need to create reports across many different fields. And this makes the learning curve increase. Right now i'm currently at a stand still because I can't figure out how to make the connections between a parent table and its child just because resources are limited on line to simple singular dbs or the relational dbs they use do not have the heavy interaction that i am requrieing. If I can't solve these issues soon I'll be dropping ruby on rails and make client/server db apps in C#.

Arevos · May 30th, 2006, 4:54 AM

Yes, the problem is that with Ruby on Rails, you sometimes have to know where to look. Still, I believe that your problem, SirBob1701, is not a problem with relationships between tables, but a problem with legacy schema. See here

Apr 7th, 2006, 2:48 PM	#1
mongeau Newbie Join Date: Apr 2006 Location: Fargo, ND Posts: 29 Rep Power: 0	Why Ruby on Rails won't become mainstream. Here is an interesting blog post objectively evaluating why Ruby on Rails won't make it to the mainstream industry. He explains that despite its technical excellence, it's only a technology experts know about, and few businesses will be willing to make the jump. The author also makes some truly valid comments regarding the usage of IDE's -- sort of going hand-in-hand regarding this recent forum topic. __________________ I wish I was you, so I could be friends with me.

Apr 7th, 2006, 5:18 PM	#2
Jessehk The Oblivious One Join Date: May 2005 Location: Ontario, Canada Posts: 648 Rep Power: 4	To me, Ruby is an amazing language. Not suited to everything, but what it does, it does amazingly well. Not having done any web development, I cannot comment on RoR. At the same time, I think the author makes very valid points. It has been demonstrated in the past that features and quality do not always determine popularity. __________________ Dr. Zoidberg: [ecstatic] I'm going to a movie... with FRIENDS!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

May 29th, 2006, 10:53 PM	#3
SirBob1701 Newbie Join Date: May 2006 Posts: 20 Rep Power: 0	Before I reply I must state that I am just now learnin Ruby on Rails. I have taken an internship at a small corperation and am developing some webased tools for them to track various aspects. I had read that Ruby on Rails was suppose to make the task quick and easy but I find there are no really indepth tutorials for Large relational databases where you need to create reports across many different fields. And this makes the learning curve increase. Right now i'm currently at a stand still because I can't figure out how to make the connections between a parent table and its child just because resources are limited on line to simple singular dbs or the relational dbs they use do not have the heavy interaction that i am requrieing. If I can't solve these issues soon I'll be dropping ruby on rails and make client/server db apps in C#.

May 30th, 2006, 4:54 AM	#4
Arevos Programming Guru Join Date: Aug 2005 Location: England Posts: 1,499 Rep Power: 5	Yes, the problem is that with Ruby on Rails, you sometimes have to know where to look. Still, I believe that your problem, SirBob1701, is not a problem with relationships between tables, but a problem with legacy schema. See here

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Programming Forums > Script Programming > Ruby

Why Ruby on Rails won't become mainstream.