Here’s a real advantage of a conference over email: I learned that Charles Nutter has an awesome Midwestern accent! I’ve got a whole new voice in my head while I read his posts, and there are a lot of them. Does Charles Nutter sleep? He seems to churn out emails and blog comments about JRuby 24/7.
On to the talk. For the record, I am not sure how I feel about the whole Rails running on JRuby inside a WAR on Glassfish stack at the enterprise data center. Sounds like a tall, tipsy stack of dinnerware to me. But I do like JRuby. It’s been really handy at C o n – w a y for calling EJBs, using mainframe proxies, and running JUnit test suites. And there’s a real possibility that the Java VM could become a great VM for Ruby.
This session’s poll:
25% of the audience are Java developers
25% ex-Java developers
15% ex-Perl users
Who uses which database?
10% MS SQL Server
Why use JRuby instead of C Ruby?
– Unicode support
– Native JVM threads
– The big pain point …
What are the biggest differences?
1) Database support. Ruby MySQL works about the same. JRuby can use JDBC, of course, and JNDI to look up connection pools. DB2 support is not 100%? (Works pretty good for me.) Oracle ActiveRecord tests are not 100%
2) Native Ruby extensions don’t work out of the box. Need porters.
3) Command-line performance because Java start-up time is slow.
Charles and Thomas demoed Goldspike, a way to package a Rails app into a J2EE WAR:
And they demoed a Glassfish gem! Hm, well, theoretically, if all this just works, it could be pretty cool. Though I dread digging through the stack trace.