On 07/12/2011, at 1:51 PM, Ben Hoskings wrote: > On 07/12/2011, at 12:54 PM, Dmytrii Nagirniak wrote: > >> My biggest concerns at this moment are: >> Warmup-time (just too slow for any kind of TDD); > > JRuby isn't designed for TDD or to run in development. It's intended to be an > industrial grade ruby for production.
I suppose you are not saying that you should run MRI in development and JRuby in production :) Even if you do, it is just not possible for me due to native Java bindings (neo4j). > (For what it's worth, I think the startup time of a rails stack on C ruby > (charitably, 5 seconds) is still far too slow to effectively test-drive > anything.) It is even slower with JRuby (it adds at least 11s to that). https://gist.github.com/1423288 -- 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.
