Ratings and Reviews
Community Rating
Average Rating: 4.4/5.0Number of Ratings: 277Number of Reviews: 4
My Review of Ruby on Rails |
||
| You have not rated or reviewed this project.Click below to rate/review. | My Rating: | |
| New Review | ||
Most Helpful Reviews
Rails certainly isn't perfect, but it's an excellent Web framework, due in large part to the power of the Ruby language. And most of the problems in the other reviews were bogus when they were written a year ago -- let alone now.
Eball said:
> No compiler means that you get to remember all the code in your head
Huh? No, no compiler means that there's no compiler. That's *all* it means. I've worked with Web frameworks in Java, and I really don't see a single advantage to compilation -- in fact, with a compiler, you have to keep in your head that the code you're editing may not be the code you're running.
> All queries are select * by default, therefore having any large objects in your database hold up app processing....you can tune your queries.
This would be a big problem -- except that, as Eball points out, you can tune your queries. It's easy to specify particular fields if you really want to. So what's the problem?
> Performance mgmt you are searching for a needle in a pile of needles...
This is true to some extent...
> soo many little problems with their uber-terse syntax.
I'm not sure how this is related to performance management.
> No threading...now this is fun...who needs threads?
Blame that on Ruby, not Rails. That's why multiple server processes have become common for serving Rails.
> Rails is a toy...a craft....not a science.
*All* programming is part craft and part science. Rails certainly isn't a toy; in my experience, the people who think it is generally have not really used it sufficiently. (People who have used Rails in depth, on the other hand, may not *like* it, but they generally don't think it's a toy.)
> if you are a junior of senior..use a real compsci language.
This, more than anything else here, points to the fact that Eball doesn't know what he or she is talking about. Ruby is far closer to being a "real compsci language" than Java, or C++, or just about anything else in common use except Lisp and Smalltalk -- and Ruby has more of a real-world ecosystem surrounding it than either of those two, which makes it easier to work with for many applications.
Most Recent Reviews
Rails certainly isn't perfect, but it's an excellent Web framework, due in large part to the power of the Ruby language. And most of the problems in the other reviews were bogus when they were written a year ago -- let alone now.
Eball said:
> No compiler means that you get to remember all the code in your head
Huh? No, no compiler means that there's no compiler. That's *all* it means. I've worked with Web frameworks in Java, and I really don't see a single advantage to compilation -- in fact, with a compiler, you have to keep in your head that the code you're editing may not be the code you're running.
> All queries are select * by default, therefore having any large objects in your database hold up app processing....you can tune your queries.
This would be a big problem -- except that, as Eball points out, you can tune your queries. It's easy to specify particular fields if you really want to. So what's the problem?
> Performance mgmt you are searching for a needle in a pile of needles...
This is true to some extent...
> soo many little problems with their uber-terse syntax.
I'm not sure how this is related to performance management.
> No threading...now this is fun...who needs threads?
Blame that on Ruby, not Rails. That's why multiple server processes have become common for serving Rails.
> Rails is a toy...a craft....not a science.
*All* programming is part craft and part science. Rails certainly isn't a toy; in my experience, the people who think it is generally have not really used it sufficiently. (People who have used Rails in depth, on the other hand, may not *like* it, but they generally don't think it's a toy.)
> if you are a junior of senior..use a real compsci language.
This, more than anything else here, points to the fact that Eball doesn't know what he or she is talking about. Ruby is far closer to being a "real compsci language" than Java, or C++, or just about anything else in common use except Lisp and Smalltalk -- and Ruby has more of a real-world ecosystem surrounding it than either of those two, which makes it easier to work with for many applications.
Just finished trying to build a mid-complexity web application using Rails.
1) No compiler means that you get to remember all the code in your head...don't go on vacation. Agile is another word for incomplete.
2) All queries are select * by default, therefore having any large objects in your database hold up app processing....you can tune your queries.
3) Performance mgmt you are searching for a needle in a pile of needles...soo many little problems with their uber-terse syntax.
4) No threading...now this is fun...who needs threads?
Rails is a toy...a craft....not a science. If you are a freshman or sophomore in college...Rails may teach you some basics..if you are a junior of senior..use a real compsci language.