tag:blogger.com,1999:blog-20975090.post7387544165247854282..comments2024-03-11T10:18:55.852-05:00Comments on Headius: Help Us Set Priorities for JRuby 1.3Charles Oliver Nutterhttp://www.blogger.com/profile/06400331959739924670noreply@blogger.comBlogger30125tag:blogger.com,1999:blog-20975090.post-18673156808366579242009-03-09T16:59:00.000-05:002009-03-09T16:59:00.000-05:00schildmeijer: Yep, I'm sure it was NetBeans.schildmeijer: Yep, I'm sure it was NetBeans.Charles Oliver Nutterhttps://www.blogger.com/profile/06400331959739924670noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-63929320181655232292009-03-09T15:47:00.000-05:002009-03-09T15:47:00.000-05:00Hi, i just saw your JRuby talk from oredev 2008 at...Hi, i just saw your JRuby talk from oredev 2008 at google video. What text editor were you using? NetBeans?schildmeijerhttps://www.blogger.com/profile/09932124537730053852noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-27009965705940225232009-03-05T11:23:00.000-06:002009-03-05T11:23:00.000-06:00Douwe: We would love to have a Performance bug rep...Douwe: We would love to have a Performance bug reported for anything you see that's slower in JRuby. Pattern matching should definitely not be slower, but it's possible you've found an edge case.Charles Oliver Nutterhttps://www.blogger.com/profile/06400331959739924670noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-81488355145240984022009-03-05T10:46:00.000-06:002009-03-05T10:46:00.000-06:00I tried jruby on rails on glassfish on my joyent s...I tried jruby on rails on glassfish on my joyent solaris host and it worked fine, although the memory footprint was too high relative to mongrel so I had to drop it. I've since dropped mongrel too for phusion passenger (mod_rails) deployed as an apache http server plugin with performance gains and even lower memory footprint over mongrel.<BR/><BR/>Can jruby on rails be set up to run via apache plugin too? If not, is that something that would be worth considering for 1.3? The argument in favor of it would be simpler setups and deployments for developers and startups with low system resources, or for those running multiple sites on one system in early business stages.<BR/><BR/>Thanks,<BR/>ReneReneRockshttps://www.blogger.com/profile/12906818749661141314noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-31109503348755512082009-03-04T16:43:00.000-06:002009-03-04T16:43:00.000-06:00Would "more Java integration" include such things ...Would "more Java integration" include such things as java.lang.String == String? Because that sure would be handy.Justinhttps://www.blogger.com/profile/13477618173340108828noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-16530429693000760152009-03-04T06:57:00.000-06:002009-03-04T06:57:00.000-06:00Hello,for me it would be* Rails deployment stuff* ...Hello,<BR/><BR/>for me it would be<BR/>* Rails deployment stuff<BR/>* Compiler #2<BR/>* PerformanceAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-29164502849082205502009-03-04T04:55:00.000-06:002009-03-04T04:55:00.000-06:00Performance is important to me, specifically I not...Performance is important to me, specifically I noticed that an app doing heavy pattern matching was slower on JRuby compared to MRI (1.1.4 was same, 1.1.5 was slower). This prevented me from using JRuby.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-25283214212156475462009-03-03T21:04:00.000-06:002009-03-03T21:04:00.000-06:001) Compiler #22) generating most of the call path,...1) Compiler #2<BR/>2) generating most of the call path, to reduce duplicate code<BR/>3) More startup perf workUnknownhttps://www.blogger.com/profile/00118441573042961263noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-27068330707463557532009-03-03T15:10:00.000-06:002009-03-03T15:10:00.000-06:00Hello Headius,as a happy user of android I would w...Hello Headius,<BR/>as a happy user of android I would welcome any improvements I could enjoy on my android. Thank you for your workAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-14363211355327229552009-03-02T18:18:00.000-06:002009-03-02T18:18:00.000-06:001. Compiler #2 / Java Integration2. Execution Perf...1. Compiler #2 / Java Integration<BR/>2. Execution Performance<BR/>3. Internal cleanupAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-79823361616027091602009-03-02T17:35:00.000-06:002009-03-02T17:35:00.000-06:00IO speed.IO speed.Daniel Bergerhttps://www.blogger.com/profile/05224445093970941579noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-25463052431930387452009-03-02T12:13:00.000-06:002009-03-02T12:13:00.000-06:00# "Pure ruby" application support, like Rails depl...# "Pure ruby" application support, like Rails deployment stuff (Warbler, AR-JDBC)<BR/># More Java integration improvement/refactoring (esp. subclassing)<BR/>There is some missing standard stuff that'd fall in Java integration esp. web integration. Like a RubySevlet.<BR/><BR/>I moved from java to jython to ruby to jruby. One thing I really liked from my jython days was PyServlet.java. I have an app from 3-4 years back still chugging along well with the simple piece of PyServlet and related code goodness. It was a great help that example came with the standard distribution and is a pretty solid piece of code. It is pretty cool to Warble-r and other command line magic stuff but there is something about the simplicity of the model. I mean it's great ruby world is/has been dominated by rails but in the standardized (web) world of java you gotta have a Servlet. It kind of complicates things when a web server team (glassfish) is selling/pitching/releasing a gem every few months for better jruby integration. There should be some not-so complicated default way. <BR/>For a RubyServlet/Filter.java all that is needed is a functional java class that has methods for instantiating an interpreter, a pool/multiple of interpreters, load/evaluate a ruby file/string, some form of caching I guess and all this with thread safety. Other standards like Rack can build on top of this I guess.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-8013812932886636982009-03-02T04:07:00.000-06:002009-03-02T04:07:00.000-06:00I vote for "More Java integration improvement/refa...I vote for "More Java integration improvement/refactoring (esp. subclassing)".Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-33196860877710339492009-03-01T23:44:00.000-06:002009-03-01T23:44:00.000-06:00I'd echo the jruby error stack like the one spewed...I'd echo the jruby error stack like the one spewed when called inside glassfish. Something to simplify web integration and deployment. For example rack is supposed to be the simplest thing but jruby-rack is like a black box. Code is hard to figure, just to get logging working properly when deployed in a container is an exercise as hard as reverse engineering a protocol.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-40362763061859824822009-03-01T22:41:00.000-06:002009-03-01T22:41:00.000-06:00I vote for Rails deployment stuff.I vote for Rails deployment stuff.Miika Leppänenhttps://www.blogger.com/profile/09971979695663520276noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-6013572365380124812009-03-01T18:43:00.000-06:002009-03-01T18:43:00.000-06:00I vote for full Ruby 1.9 compatability (assuming i...I vote for full Ruby 1.9 compatability (assuming it's not already there).<BR/><BR/>Also, allow time for FFI documentation/support/evangelism. It would be great to get all those ruby gems with C dependencies converted.<BR/><BR/>Once we can run our apps with caring if we're on MRI or JRuby, the sky is wide open!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-81294004637732923292009-03-01T13:15:00.000-06:002009-03-01T13:15:00.000-06:00The biggest issue we hit today is not with JRuby i...The biggest issue we hit today is not with JRuby itself, but with running Rails on JRuby in an app server. Glassfish v2.1 throws a lot of errors and warnings that are not easily decipherable, and the deploy memory leaks are really bad. <BR/><BR/>I would focus some time on getting that aspect of the stack really solid. I know this is not really JRuby-core, but it is a critical part of the experience.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-70513478018847046052009-03-01T12:21:00.000-06:002009-03-01T12:21:00.000-06:00Charles,The #1 killer feature for JRuby (IMHO) is ...Charles,<BR/><BR/>The #1 killer feature for JRuby (IMHO) is being able to use JRuby classes from other JVM langs with as little fuss as possible. Other JVM langs have been able to pull this off and it has made their interoperability a compelling proposition. My guess is that this is perhaps the hardest thing to do of the options you threw out there. <BR/><BR/>Thank you for asking!Mariohttps://www.blogger.com/profile/09735459767789832285noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-58309000763674259952009-03-01T11:19:00.000-06:002009-03-01T11:19:00.000-06:00Hi Headius,for me it's Performance (of Rails stack...Hi Headius,<BR/><BR/>for me it's Performance (of Rails stack to be exact). I don't really care about anything else JRuby has to offer at this point :(.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-8332944509730690622009-03-01T07:14:00.000-06:002009-03-01T07:14:00.000-06:001. Performance2. "Compiler #2" to produce normal J...1. Performance<BR/>2. "Compiler #2" to produce normal Java classes from Ruby<BR/>3. More Java integration improvement/refactoring (esp. subclassing)khelllhttps://www.blogger.com/profile/13398340882612317196noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-41983378771590994492009-03-01T01:34:00.000-06:002009-03-01T01:34:00.000-06:00Hey Headius, thanks for asking ;-)Ruboto rocks. I ...Hey Headius, <BR/><BR/>thanks for asking ;-)<BR/><BR/>Ruboto rocks. I guess the following two would help it the most?<BR/><BR/>"Improvements to AOT compilation" and "Compiler #2".<BR/><BR/>Btw. (a) how big is the app you deployed? (b) Yes, the BufferedReader warning in the log is really annoying, especially because standard libraries use the default constructor too.Marianohttps://www.blogger.com/profile/04576024486566426295noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-32408167327537779052009-03-01T00:40:00.000-06:002009-03-01T00:40:00.000-06:001. Startup perf work 2. Performance general 3. Rai...1. Startup perf work <BR><BR/>2. Performance general <BR><BR/>3. Rails deployment <BR>Lars Westergrenhttps://www.blogger.com/profile/02654687571384000146noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-10549571186563538532009-02-28T23:00:00.000-06:002009-02-28T23:00:00.000-06:00Don't bother with Ruby 1.8.7 support. If people wa...Don't bother with Ruby 1.8.7 support. If people want these new features, they should just go ahead and switch to 1.9-mode.<BR/><BR/>I'm most interested in the promise of the improved compiler. Clojure interop would be interesting too for folks who want to push the FP envelope.Philhttps://www.blogger.com/profile/12517691336187602116noreply@blogger.comtag:blogger.com,1999:blog-20975090.post-25708403961156612452009-02-28T22:36:00.000-06:002009-02-28T22:36:00.000-06:001. "Compiler #2" to produce normal Java classes fr...1. "Compiler #2" to produce normal Java classes from Ruby<BR/>2. Performance<BR/>3. More Java integration improvement/refactoring (esp. subclassing)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20975090.post-2426392540915636592009-02-28T19:30:00.000-06:002009-02-28T19:30:00.000-06:00In no particular order:AOTCompiler #2Execution per...In no particular order:<BR/><BR/>AOT<BR/>Compiler #2<BR/>Execution performance ( keeping at or near the head of the pack. )Gabriel Correahttps://www.blogger.com/profile/06310325192707471984noreply@blogger.com