This post originated from an RSS feed registered with Ruby Buzz
by Obie Fernandez.
Original Post: Refactoring in Java vs. Ruby
Feed Title: Obie On Rails (Has It Been 9 Years Already?)
Feed URL: http://jroller.com/obie/feed/entries/rss
Feed Description: Obie Fernandez talks about life as a technologist, mostly as ramblings about software development and consulting. Nowadays it's pretty much all about Ruby and Ruby on Rails.
Next time you hear "Refactoring in dynamic languages is not possible or at least very, very difficult" or "You can't refactor Ruby, because you can't do static analysis", send them over to Murphee.
There's a problem with claims that everybody repeats with a knowing look on their face... they might just be Bullshit.
Lots of good stuff in there that I think most of us doing Ruby know about, but it's great to see it come up on JRoller, aimed at the Java people.
My 2 cents... I believe IntelliJ actually does a fairly good job with rename refactorings within textual resources, but in Java-land, with the multitude of XML configs and reflection going on nowadays, you're not that much better-off (for some refactorings) than the situation Ruby is in right now. The other point I think he failed to emphasize very well: Forcing you down a path of air-tight unit testing is a GREAT thing.
Previous Topic
