tag:blogger.com,1999:blog-6711253058798651435.post4808080793396208656..comments2011-11-29T13:51:49.324+11:00Comments on Art of Programming: Issues switching to JRuby from MRI 1.9Dmytrii Nagirniakhttps://profiles.google.com/116807208912177719748noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6711253058798651435.post-82134095468788194242011-11-29T13:51:49.324+11:002011-11-29T13:51:49.324+11:00Totally with you on this. But real world seems to ...Totally with you on this. But real world seems to be a bit different :)Dmytrii Nagirniakhttp://www.blogger.com/profile/00858741986129879076noreply@blogger.comtag:blogger.com,1999:blog-6711253058798651435.post-10096925514556313152011-11-29T13:22:36.904+11:002011-11-29T13:22:36.904+11:00Yet another reason to avoid C-extensions. When sel...Yet another reason to avoid C-extensions. When selecting dependencies for a new project, I prefer to select pure-Ruby libraries or FFI bindings (https://github.com/ffi/ffi#readme). Pure-Ruby libraries should be faster on Rubinius/JRuby. FFI bindings work perfectly on both MRI and JRuby.<br /><br />If developers want faster Ruby code, they should help make MRI faster (or switch to Rubinius/JRuby), instead of writing more code in C.Postmodernhttp://postmodern.github.com/noreply@blogger.com