Pet peeve: @twitter's description of migrating "from Ruby to the JVM": they're not orthogonal o_O
-
-
-
Replying to @moonpolysoft
@moonpolysoft the JVM is hard! let's write our own generational garbage collector for REE instead o_O1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@moonpolysoft yeah except your the only person in the world who has good real-world perf experience w jruby.4 replies 0 retweets 2 likes -
Replying to @jamesgolick
@jamesgolick@bascule@moonpolysoft pretty much everyone I know who's made the MRI -> JRuby transition has done so for performance1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@moonpolysoft me too. you're just the only one I've heard report a good result.1 reply 0 retweets 0 likes -
Replying to @jamesgolick
@jamesgolick@moonpolysoft as another data point,@SpiceWorks reported a 4X increase in throughput going from MRI -> multithreaded JRuby2 replies 0 retweets 0 likes -
@moonpolysoft @jamesgolick @Spiceworks seems good bro
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.