tag:blogger.com,1999:blog-20975090.post4772109654520682016..comments2026-02-05T05:43:08.642-06:00Charles Oliver Nutterhttp://www.blogger.com/profile/06400331959739924670noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-20975090.post-59500422031105716572007-03-07T20:09:00.000-06:002007-03-07T20:09:00.000-06:00I was the guy at No Fluff telling you that jruby wouldn't run the Metakoans Ruby Quiz code. Well, I'm glad to report the latest version does!Geoffhttps://www.blogger.com/profile/10269884442141861327noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-78971703558183434142007-03-07T04:56:00.000-06:002007-03-07T04:56:00.000-06:00Congrats for this new release. I'm happy tighter Java integration will get a higher priority, as my primary interest for JRuby is to have access to the enormous amount of Java libraries from Ruby.<BR/><BR/>Raphraphinouhttps://www.blogger.com/profile/10541528354162666577noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-11943473951839722362007-03-07T03:52:00.000-06:002007-03-07T03:52:00.000-06:00You guys made amazing progress on JRuby!<BR/><BR/>Quick question on the footprint. If you are going to load multiple JRuby run-times, would each run-time drag in its own copy of JVM?<BR/><BR/>We are doing some heavy duty performance testing of DB2 on Rails (see http://db2onrails.com)and I would really like to see the difference in capacity between Ruby on Rails and Mongrel and JRuby.Leonhttps://www.blogger.com/profile/17772925377386790449noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-74068374610830194152007-03-06T14:51:00.000-06:002007-03-06T14:51:00.000-06:00Marcus: Basically, instead of having multiple processes, a Rails app deployed to an app server would have multiple JRuby runtimes to handle the requests. This is far lighter-weight, easier to manage, and it will scale to the load. You certainly don't need to have multiple app server instances, although if you choose to do that (i.e. through clustering) you will have that option too :)Charles Oliver Nutterhttps://www.blogger.com/profile/06400331959739924670noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-41743460640778466062007-03-06T12:59:00.000-06:002007-03-06T12:59:00.000-06:00Nice work and congrats!<BR/><BR/>A thing I've been wondering regarding Rails, java and java app servers (or serlvet containers): In real world Rails applications you have to deploy several server processes to handle parallell requests due to Rails non-thread safety. How is this supposed to be handled with java app servers? I mean, you can't really deploy a ton of JBoss, Tomcats or even Jettys. <BR/><BR/>So how are Rails applications really supposed to work on the java platform?<BR/><BR/>/MarcusUnknownhttps://www.blogger.com/profile/14550480981193617186noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-19955429511322970552007-03-06T12:57:00.000-06:002007-03-06T12:57:00.000-06:00Anonymous: I'd love to have the AOT compiler done by the 1.0 release, but it's not as high a priority as having the JIT working well and general performance running faster than MRI. Complete, flawless AOT compilation of Ruby is quite complicated, and I don't plan on delaying the 1.0 release to finish the last 5 or 10% of really hard compiler features.Charles Oliver Nutterhttps://www.blogger.com/profile/06400331959739924670noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-55990249764623267722007-03-06T12:03:00.000-06:002007-03-06T12:03:00.000-06:00Great job. I enjoyed your world tour blogs too. Would the AOT compiler be part of the 1.0 release?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-31039001513577690152007-03-06T11:45:00.000-06:002007-03-06T11:45:00.000-06:00Way to go Charles! Congratulations!Anonymousnoreply@blogger.com