I think the point about the question is that both of those answers can be very interesting and spark conversation about your knowledge about, and approach to, computer programming as problem solving.

Yep. 20 years ago it would show that the OP is at a stage where they love what Ruby is doing with code readability and cool ActiveSupport mixins etc. but maybe hasn't considered there are some performance limitations that hit a lot of the early Ruby success stories, now it would show a more experienced engineer that is aware of those nuances.