Ah ha! Victory is mine!  She takes her first step towards the Groovy darkside 
without even knowing it. None of this Ruby rebel scum for her! When you can 
snatch the closure from my hand DBA, then your training will be complete. 
Happy Holidays! 

Todd R. Ellermann
VP of Engineering VirtualTourist.com

Founder Webagogy.com
Researcher Betterwebapp.com

805-850-8044 cell

Does getting an ASU MBA with existing UofA BSCE make me a SunCat? or a 
Go Cats! ...said with a Devilish grin ;)

To: jug-discussion@tucson-jug.org
Cc: jug-discussion@tucson-jug.org
Sent: Tuesday, December 9, 2008 1:47:22 PM
Subject: Re: [jug-discussion] JRuby vs. Groovy (was: Any News on the Holiday 

heheh  and my language of choice...

Thanks all.  It'll be good to put
 your faces to your names at the party. 

Liz, Data Base Administrator,
Methods Engineering


"Chad Woolley"
12/09/2008 02:11 PM 
Please respond to
 To jug-discussion@tucson-jug.org  
Subject Re: [jug-discussion] JRuby vs. Groovy
(was: Any News on the Holiday Party?) 


It was mentioned in the previous thread that this
is not a web app.

As for JRuby vs. pure Ruby.  However, this is the JUG list, and the
question on JRuby performance was my chance to be a troll with a
point, especially since there's been Groovy vs. Ruby debates on here
before ;)

Depending on the target deployment environment (windows?  lots of
users?  Intranet?) JRuby might still be a better choice, since the
is ubiquitous (and native Ruby on Windows still sucks).

-- Chad

PS: Don't forget the JOrganic JJelly with a side of JJuice...

On Tue, Dec 9, 2008 at 1:59 PM, nlesiecki <[EMAIL PROTECTED]>
> If I was from-scratching a website, I'd definitely look at JRuby on
> With JPeanut sauce on my JTofu.
> Nick
> On Dec 9, 2008, at 12:04 PM, Chad Woolley wrote:
>> Here's the latest performance numbers on JRuby:
>> http://antoniocangiano.com/2008/12/09/the-great-ruby-shootout-december-2008/
>> Summary - JRuby is doing very well; came in second after Ruby
1.9; and
>> compatibility is good and getting better all the time.
>> Ok, troll time:
>> My opinion - definitely try JRuby over Groovy.  You get all
>> benefits of the Java ecosystem: native calls to java libraries,
>> execution, JIT compilation, packaging, war/ear-based deployment,
>> etc.  Most importantly, however, you get a language that
was designed
>> to "make people happy".  Most Rubyists - especially
those with
>> experience in other languages - agree it achieves this goal well.
>> As for Groovy, I still say it is an attempt to make a static language
>> (Java) appear dynamic.  They've done a decent job, but when
you really
>> compare it to using native Ruby, the warts and sharp edges poke
>> through.
>> The only argument I see in favor of Groovy is integration with
>> Java ecosystem, which JRuby effectively negates.  Conversely,
>> language or syntax preference or prejudice aside, the Ruby ecosystem
>> is also very rich (rubygems and github), and you cannot take advantage
>> of this with Groovy.  Why not be able to choose from the
best of both
>> worlds?
>> Java is dead, long live the JVM.  JRuby FTW in the enterprise.
>> -- Chad
>> On Mon, Dec 8, 2008 at 3:45 PM, Todd Ellermann <[EMAIL PROTECTED]>
>>> One more side note.  JRuby runs on the JVM as well, and
for a while was
>>> out
>>> performing the native Ruby interpreters. Not sure if that
is still true.
>> ---------------------------------------------------------------------
>> 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]

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


This email (and all attachments) is for the sole use of the intended 
and may contain privileged and/or proprietary information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.

Reply via email to