On Wed, Dec 7, 2011 at 12:54 PM, Dmytrii Nagirniak <[email protected]> wrote:
> Hi, > > I wonder what arguments do you have against JRuby and what experience have > you had with it? > Short version: it will give you pain, but it's sometimes worth it. > > My biggest concerns at this moment are: > > - Warmup-time (just too slow for any kind of TDD); > - Stacktraces (yes, it's worth mentioning! :) ) > - Gems compatibility; > > You've covered it pretty effectively. Used JRuby at my last job. There are workarounds for the warmup time on tests, but we never _quite_ got them working. We also found that our hour-long cuke run would get in to some weird GC fail-loop where it would OOM no matter how much memory you gave the JVM. Also also we had weirdness with the JDBC wrapper & ActiveRecord & background tasks. We had the problem where when investigating errors we always had to wonder "is this a common problem, or is this a JRuby incompatability?" There are good reasons to use JRuby over MRI (performance & Java integration). There are too many downsides to make it my 'default' stack. The reason for this question is basically neo4j database. I can't see all > its benefits with REST API. > This leaves me with native Java bindings (and this brings me to JRuby). > > See above. If you're married to that stack, that's a great reason to use JRuby. -- Michael Pearson -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
