16 ms·
If a team is using different versions/runtimes of ruby I would have to agree this is an organizational feature in some cases. If you're working on a webapp you
by mark_story 14y ago
If a team is using different versions/runtimes of ruby I would have to agree this is an organizational feature in some cases. If you're working on a webapp you should be aiming to make as few differences between a development box & production as possible. Its unlikely that you have jruby & mri in production, wherein lies the failure.
- steveklabnik 14y agoSquare is one example of a company which famously develops in MRI but deploys JRuby to production.
- mark_story 14y agoThat sounds crazy to me, but I have very little experience with ruby. In PHP/python doing that can be unpleasant.
- yb66 14y agoOne big reason for this is the different start up times between versions of Ruby, especially JRuby vs anything else. It can impact your development time quite a lot. If you know they're compatible and you have specs there should be little problem with doing this. I completely disagree with DHH btw. Checking in generated files is a no no in my book, as is telling other people that using differing version managers is organisation failure, as is this kind of teenager's-diary style blog post. He needs to take a step back and breathe.