This post originated from an RSS feed registered with Java Buzz
by dion.
Original Post: Code-to-learn ratio: Getting work done with Ruby
Feed Title: techno.blog(Dion)
Feed URL: http://feeds.feedburner.com/dion
Feed Description: blogging about life the universe and everything tech
I have been working on a fun new project, where I get to work in Ruby.
After spending some time submerged in Ruby land, I am having some interesting thoughts.
The biggest point is that the code-to-learn is very high in Ruby.
You go from thinking "Hmm, I need to send an email in my code...." having never touched an email module, to writing the simple Net::SMTP code in minutes.
This happens with more complicated parts and pieces too, and I find myself spending way less time on websites and Google trying to work out a bizarre issues, and more time writing code to get my work done.
Ruby could look ahead and not have to read my def before I use it
I admit it. I like { } as delimiters. A lot more than "end end end end"
IntelliR :(
That being said, these are all MINOR nitpicks (apart from IntelliR). I am having a great time solving problems at a nice, high, functional level of abstraction.
Oh, and I haven't had a RuntimeException due to passing in the wrong type yet.