On 07/12/2011, at 1:09 PM, Michael Pearson wrote: > On Wed, Dec 7, 2011 at 12:54 PM, Dmytrii Nagirniak <[email protected]> wrote: > Short version: it will give you pain, but it's sometimes worth it.
It feels like this pain is around every corner. Something very small, but there is always "something" :) > Used JRuby at my last job. There are workarounds for the warmup time on > tests, but we never _quite_ got them working. Got the same feeling. I tried could of those things, but didn't feel it's worth the effort. > 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. Can you give some more details on this if you still remember those? Just to be aware of. Do you think it could have changed since then? > We had the problem where when investigating errors we always had to wonder > "is this a common problem, or is this a JRuby incompatibility?" So far I Google kind of helps with this. I either search for the error or search for the error with JRuby in it. But I definitely see what you mean. > There are good reasons to use JRuby over MRI (performance & Java > integration). There are too many downsides to make it my 'default' stack. Right. Makes a lot o sense. I tried to stay within MRI, but the REST API just isn't good enough. So I quit on it. Hopefully I won't regret this decision in 2 years time :) -- 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.
