JRuby Great Addition To Java Development

An anonymous reader writes "JRuby combines the object-oriented strength of Smalltalk, the expressiveness of Perl, and the flexibility of the Java class libraries into a single, efficient rapid development framework for the Java platform. This article introduces JRuby, a sophisticated addition to your Java development toolbox."

Comments

Re:So... work with me here....

[Fweeky]

No, it's a tree-based interpreter like the standard Ruby one AFAIK.

I'm still wondering why we're seeing a story on this so long after it's release, when the likes of Rails, one of the more exciting Ruby libraries in recent memory, gets completely ignored.

Of course, nobody here would really be interested in a powerful, easy way to develop web applications with practically zero configuration. It's just not *fun* without 800k of XML just to configure your ORM library :/

other languages

[Intrigued]

To my understanding, this is one script interpreter that is being developed for Java. It offers ease of use for people accostumbed to working with Ruby.

For a larger view of the language development being done similar to this, take a look at List of Java virtual machine languages.

I should think that most people will find at least something that appeals to them.

Re:So what exactly is the difference...

[bonniot]

Ruby and Groovy are different languages. They happen to be both scripting languages, and to have an implementation that runs on the jre (Java Runtime Environment), that's all.

The JRuby article is part of the alt.lang.jre series, with announced articles about "Rhino, Nice, and NetRexx, and many other exciting alternate languages for the JRE". It looks like the articles are coming in this order, one around the beginning of each month.

JRuby versus Java [code comparison - short]

[tod_miller]

JRuby

require 'java'
module Swing
include_package 'java.awt'
include_package 'javax.swing'
end
module AwtEvent
include_package 'java.awt.event'
end

$calculator = Swing::JFrame.new
class << $calculator

def init
end

end

$calculator.init
$calculator.setSiz e(400, 400)
$calculator.setVisible(true)

versus Java

import javax.swing.JFrame;
public class Calculator extends JFrame {
public Calculator(){
super("Slashdot Rul3z");
setSize(400, 400);
setVisible(true);
}
public static void main(String[] args) {new Calculator();}
}

and we have a winner

Re:JRuby versus Java [code comparison - short]

[bzhou]

vs. Jython

from java import awt
from pawt import swing

labels = ["0", "1", "2", "+",
"3", "4", "5", "-",
"6", "7", "8", "*",
"9", ".", "=", "/" ]

keys = swing.JPanel(awt.GridLayout(4, 4))
display = swing.JTextField()

def push(event):
display.replaceSelection(event.actionCommand)

d ef enter(event): # <= def, slashdot formatting bug?
display.text = str(eval(display.text))
display.selectAll()

for label in labels:
key = swing.JButton(label)
if "=" == label:
key.actionPerformed = enter
else:
key.actionPerformed = push
keys.add(key)

panel = swing.JPanel(awt.BorderLayout())
panel.add("North ", display)
panel.add("Center", keys)
swing.test(panel)

Re:JRuby versus Java [code comparison - short]

[Eivind Eklund]

... and we have a loser writing.

When you have zero clue how to write the language, I suggest you shut up.

The equivalent Ruby is (sorry about the lack of indentation - Slashdot seems to eat it):

require 'java'
include_package 'javax.swing'

class Calculator < JFrame
def initialize
super("Slashdot Rul3z")
setSize(400, 400)
setVisible(true)
end
end

Calculator.new()

That's exactly one require-line and two blank lines more than your non-idiomatically-indented Java with missing newlines. It is one line less than what I'd consider normal amount of spacing - a newline after the import statement, a newline between the methods, and the {}-block for main actually spaced out.

Eivind.

Re:JRuby versus Java [code comparison - short]

[tod_miller]

When you have zero clue how to write the language, I suggest you shut up.

*waves* hello, you must be new around here, *points at article* If you would like to read that while you wait, we call it reading the article.

I copy and pasted that code out of the article - I didn't make it up.

hint
The article was about JRuby.

And it wasn't a penis measuring contest, but a legibility contest. Now I can read java easier than JRuby because I read it daily. But looking at the redundant entropy in the bytes (I won't huff it for you) I can tell that this code looks more complicated.

So take that ruby out of your ass and RTFAYFT.

(readthefuckingarticleyoufuckingtwat)

end

Please enjoy.

About that name

[HughsOnFirst]

So when I tell somone that this is the right tool for the job , how am I supposed to pronounce it?
ja-ru-bee? ( gummie candy treat perhaps? )
har-you-bee ?
or jay-ru-bee as though it were named after Lee Harvey Oswald's killer Jack Ruby ( J. Ruby ) ?

Or, if you're writing a small utility...

[tcopeland]

...just skip Java and go with Ruby.

I needed a small app to analyze SQL query usage, and Ruby worked great. As long as you're conscientious about writing unit tests, you won't miss Java's static typing at all.

Hrmph.

[Estanislao Mart�nez]

Last I looked (which can't have been over a month ago), JRuby was far from being ready for prime time. I'm a Ruby guy myself, yet I really wouldn't touch JRuby just yet, unless my purpose was to develop it myself.

Groovy is, IMO, a near-clone of Ruby designed from the ground up to integrate with Java, and would probably be a better choice than JRuby. I think the Groovy documentation isn't quite there yet, tugh.