Many noted that most of the topics of concern to practitioners, and to the InfoQ communities, like architecture, agility, SOA, Ruby, and.net, are essentially non-existent in academic curricula.
很多人指出，关注从业者和InfoQ社区(比如架构、敏捷、SOA、Ruby、。Net)的大部分议题在学术课程里基本上并不存在。
This is not a criticism of Ruby on Rails developers, of course; it's simply a consequence of non-specialization; in some cases, Rails developers may be experts in both areas.
当然，这并不是在责怪RubyonRails开发人员；这是非专业化导致的后果；在有些情况下，Rails开发人员有可能是这两个领域的专家。
One of those clients, Carrot, has been explicitly written to get back to non-event-driven, synchronous Ruby while preserving much of the clean style in which the event-driven Ruby API is written.
其中的一个客户端Carrot很明显使用了非事件驱动的同步ruby架构，因此，这个客户端在使用事件驱动的RubyAPI的时候，风格非常简洁。
Parsing is the Achilles' heel of Ruby implementations and for us it is a non-issue.
解析就是Ruby的阿基里斯的脚跟，而且对我们来说毫无意义。
Using RVM, how to ensure gems and non-gems see the same version of ruby?
使用RVM，如何保证宝石和非宝石看到红宝石相同的版本？
Using RVM, how to ensure gems and non-gems see the same version of ruby?
使用RVM，如何保证宝石和非宝石看到红宝石相同的版本？
应用推荐