Slashdot Mirror

← Back to Stories (view on slashdot.org)

Using the Ruby Dev-Tools plug-in for Eclipse

Posted by ScuttleMonkey on from the more-than-one-way-to-skin-an-app dept.

An anonymous reader writes "IBM Developerworks is running an article that introduces using the Ruby Development Tools (RDT) plug-in for Eclipse, which allows Eclipse to become a first-rate Ruby development environment. Ruby developers who want to learn how to use the rich infrastructure of the Eclipse community to support their language will benefit, as will Java developers who are interested in using Ruby."

2 of 108 comments (clear)

  1. Ruby..... by james_in_denver · · Score: 4, Insightful
    It rocks...... I'm using Ruby at work to parse millions of lines of source code across 4 different systems and link that back to literally hundreds of requirements documents. The end result is stored in a database and made available via "Ruby on Rails" . It's saved the client literally hundreds of hours of debugging and integration time, and the "documentation"? It never gets out of date... Just run the programs against the source code and document repositories nightly and everything is current.....

    And Eclipse? simply the best development IDE available IMHO...... And all of that in only a few thousand lines of code.....

  2. Re:What doesn't Eclipse do? by Dan+Farina · · Score: 4, Insightful

    ...Truly the emacs of this generation.

    From vi, to emacs, to eclipse (ratios of memory usage in each generation maintained!)

    I actually do not like the eclipse editor component as much as emacs. Ideally, I'd want the GUI-esque browsing/completion/etc of eclipse with the emacs editor. (There have been attempts at this, but none of them feel "right")

    It's also harder to write ad-hoc extensions to an eclipse plugin, which is one large benefit emacs has over it.

    df