Comments on: Ruby on Rails 1.0 is out

By: Anonymous

Anonymous — Thu, 10 Jan 2008 10:07:19 +0000

not sure what to use

By: ajay reddy akiti

ajay reddy akiti — Tue, 29 May 2007 08:39:05 +0000

how can i access the c language code in ru by on rails

By: lgomez

lgomez — Sun, 05 Feb 2006 08:04:43 +0000

People, I think you are wasting your time discussing this. If RoR seems the way it appears to you, fine. Feel free to use something else. Python, Java, ASP.NET, PHP, whatever. These are tools. You should be thankful you have options. I myself have used PHP primarily for over seven years, ASP at some point (before PHP), some Python and now Ruby and Ruby on Rails.

Some fit certain projects and others fit other projects. I like the Rails philosophy to a certain degree and think we could all benefit from it. Again, these are tools. If you don’t see them as tools and if you don’t see the advantage of having options and accepting that some are better for certain things, then IMO you need to stop breathing code and go get some air.

Not to be rude but I’ve heard this discussion many times already (with and without RoR).

Have a nice day.

By: Jeff

Jeff — Sun, 18 Dec 2005 22:37:44 +0000

I am intrigued by the hype of Rails and I enjoyed watching the blog-in-15-minutes overview. I think that is what it should be looked at too – an overview. There is more behind Rails (such as the power of Ruby) that leaves lots to be learned by us all.

I am an ASP.Net 1.1 developer and I just now got a chance to look at ASP.Net 2.0 and was surprised at how much time they spent reducing the time for the developer to do common tasks. In rails, it is a few lines of code to get the ‘insert’, ‘edit’, ‘delete’ functionality … in ASP.Net 2.0 it is a few mouse clicks. The new IDE is (free) way better than Visual Studio 2003 – which I never used because it sucked and stuck with Dreamweaver.

Anyhow, Rails is wicked-awesome from my brief look into it. I’ll definately get a project or two going on it and add it to my toolbelt of languages to use for projects. Many of already said it in these comments but Rails, PHP, CF, ASP.Net , Java etc. all have their place and the choice is up to you as the developer to decide what is right for the tasks at hand.

Good luck to everyone.

By: bonefry

bonefry — Sat, 17 Dec 2005 05:53:28 +0000

Oh, I forgot, there is another problem with Ruby on Rails.
The Rails community became too arrogant in relatively little time.
It doesn’t help promoting Rails simply because Ruby is still considered a toy.

By: bonefry

bonefry — Sat, 17 Dec 2005 05:49:22 +0000

Problem with Ruby (the platform) is speed.

When talking about multi-tier web applications we also need pure processing power. The current sollution in Ruby is to drop to C code … and that, from a productivity perspective, sucks.

Also, because Ruby cannot even have an XML parser written in pure Ruby that doesn’t suck, many libraries come with components written in C, making deployment a nightmare.

When it comes to Rails … my main problem with it is the poor internationalization support, although overall is a good framework.
Another problem would be the AJAX support that looks childish.

IMHO, component and event-based web development (ASP.NET, JSF, Tapestry) is the way to go.

By: heartburn

heartburn — Fri, 16 Dec 2005 06:25:09 +0000

No that’s silly. I am learning it right now. You know very well that I’m subscribed to this thread and my email icon blinks whenever someone posts. I can’t have spent more than 45 minutes total here and that was trying to get answers that don’t seem to be forthcoming. So I think it’s unkind suggest that I’m sitting around doing nothing but staring at this thread when I should be studying.

By: Clenard

Clenard — Fri, 16 Dec 2005 06:23:37 +0000

I’ve played around with RoR and I’m still not sold. I’d much rather go with Python and use TurboGears just because Python seems to be a MUCH more mature language in general.

RoR IMO is a cool framework – but people pump it up a little too much. It’s not an “EASY” Language to learn… you STILL have to learn ANOTHER LANGUAGE that will take you 10 times the time to learn it than it would take you to build 2-3 New Projects using your existing Languages, so what’s the point? I’ve been hearing “Rapid Development” on every Blog online but it just doesn’t make sense to me to learn, yet ANOTHER language to get things done a little faster??? I’ve even heard “ROR Brought us AJAX” somewhere… funny, I thought JavaScript brought us AJAX (other than Jesse James Garrett ;) ). PRADO was using “AJAX” before it was coined “AJAX” but, since it was “just another framework” it’s still “just another framework”.

The thing I do like about RoR is the fact that they brought Video’s rather than boring old Text Documents… But, I’ll stick to PHP and wait for the Zend Framework to hit the Community =) I just see RoR like Audi’s in America… yeah, they’re cool, they’re fast, goood looking, etc — but why do I need it? What’s the down-side to it? There’s definately better choices out there, right?

Hopefully, as I’ve mentioned other places, Zend will do the same as RoR did with the Video’s, but with more examples than RoR.

By: ikarys

ikarys — Fri, 16 Dec 2005 05:54:08 +0000

BTW, I was the Anonymous poster that ikeo quoted. I dunno why it made me anonymous :(

:) that time to sit still and learn, is the time you spent discussing in this thread.
It’s that easy!

By: heartburn

heartburn — Fri, 16 Dec 2005 04:31:49 +0000

A long time ago, at a telephone company far, far away, we used Clipper for a DOS based order entry system. (for you youngsters, clipper was the “dirty little secret” of programming shops that needed to create database backed DOS apps fast.) We hated Cliper. A day didn’t go by that We didn’t curse Clipper.

Then one day, Microsoft introduced VisualBasic 1. What a wonderful day that was! It got great press. Everyone seemed to love it. And it created Windows apps without C! We rejoiced. We made pretty screens, we popped up dialogs… we were happy.

We were happy until we tried to meet our requirements. As our code piled up behind buttons, we struggled with basic functionality like communications and printing. How we longed for the days of Clipper.

The moral of the story is… I’m not sure :(