I believe it's a combination of both. Coding in ruby changes the way
you think about problem solving. It really does. Of course, I'm
sure we all said the same thing about Java when we first picked it up ;)
Given a specific problem to tackle, I could easily write the same
number of lines of ruby as I would in Java if I chose to. If I
continue to "think in Java", my ruby code will look (structurally)
like Java. That's actually a natural progression that people will
make as they learn to "think in Ruby". There are so many more ways
to reduce your code in Ruby than in Java, without taking away or
hiding what you intended to do. It really takes me aback sometimes,
almost to the point of disbelief. I struggle getting to optimal code
structure because I'm so used to being verbose with Java.
Sorry, I'm not trying to push Ruby on you guys, I just want to be
honest about my experience.
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 19, 2007, at 6:53 PM, Ted Husted wrote:
On 3/19/07, James Mitchell <[EMAIL PROTECTED]> wrote:
If you ever do get the Agile Web Development with Rails book or pdf
and build the Depot app along with the book, you'll be asking
yourself why anyone does anything other than Rails. You've been
warned!
Do you credit Rails with that, or that Ruby is not verbose, so that
there are fewer lines of code?
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
