Turbogears 将如何达到 Ruby on Rails 的临界质量？
自从我有 Python 背景以来，我一直在使用 Turbogears，但看到所有可用的 Ruby on Rails 资源，我不禁感到一阵嫉妒。
例如，要粗略比较资源量，请查看 http://www.google.com/trends?q=turbogears%2C+ruby+on+rails
Turbogears 需要什么才能达到 Ruby on Rails 的临界质量？一个大型插件库？性感营销？
I've been using Turbogears since I have a Python background, but I can't help feeling a pang of jealously seeing all the Ruby on Rails resources available.
For example, for a crude comparison of the volume of resources, check out http://www.google.com/trends?q=turbogears%2C+ruby+on+rails
What would it take for Turbogears to reach the critical mass of Ruby on Rails? A large repository of plugins? Sexy marketing?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我认为 Turbogears 的缺点是工作起来有点复杂（我的意思是非平凡的使用 - 快速启动系统很好），似乎一直在变化（不同的版本有不同的 ORM， auth 库、Web 后端、模板引擎等），以及在其短暂的生命周期内拥有不同的维护者等。因此，让其正常工作的人通常出于必要而比您在现实中看到的更加自给自足。 RoR 或 Django 世界，因此对确定严格的规范、良好的文档或“传播”技术不太感兴趣。
举个后者的例子，当 SourceForge.net 宣布他们将 TurboGears 与 MongoDB 结合使用时，您可能会认为社区或维护人员会接受这一事实，这表明 Turbogears 是对 NoSQL 新兴趣的绝佳选择。但相反，大家似乎集体耸了耸肩，好像在说：“是的，我们一直都知道 TG 很棒。有什么大不了的？”：）Turbogears 的维护者显然使用了 MongoDB，但邮件列表上对此的讨论很少，文档中也没有任何相关内容。因此，任何看过 Sourceforge 报道的人都会去 TG 网站，环顾四周，最终会感到有点迷失，甚至可能感到失望。
因此，我认为，除非 Turbogears 现有的维护者和专家社区能够投入更多的时间向外看并考虑如何扩大框架的吸引力，否则社区将继续保持相当小的规模和专注度。
I think Turbogears suffers a bit from being a little bit complex to get working (and by that, I mean non-trivial use - the quickstart system is fine), from seeming to be in flux all the time (different versions have different ORMs, auth libraries, web back-ends, template engines, etc), from having different maintainers over its short lifespan, etc. So the people who get it working are usually, through necessity, a bit more self-sufficient than you might see in the RoR or Django world, and thus less interested in nailing down firm specs, good documentation, or 'evangelizing' the technology.
For an example of the latter, when SourceForge.net announced that they were using TurboGears with MongoDB, you'd think the community or the maintainers would jump on that fact, showing that Turbogears is a great choice for the new interest in NoSQL. But instead there seemed to be a collective shrugging of the shoulders, as if to say, "yeah, we knew all along that TG was that great. What's the big deal?" :) The maintainer of Turbogears apparently uses MongoDB, but there's scant discussion of it on the mailing list and nothing about it at all in the docs. So anybody who saw the Sourceforge coverage is going to go to the TG site, look around, and end up a bit lost, maybe even disappointed.
So, I think that unless the existing maintainers and expert community of Turbogears are able to devote more time to looking outwards and considering what will broaden the appeal of the framework, the community will continue to stay quite small and focused.
目前，Ruby 和 Python 都没有足够的动力来支持多元化的 webdev 社区。在我看来，以下是我们作为 Ruby 和 Python Web 开发人员应该遵循的步骤列表：
因此，正如其他人已经建议的那样，暂时保持低调并使用 Rails 或 Django 执行步骤 (2)。 ;)
Right now, neither Ruby nor Python have enough momentum to afford diversifying webdev community. In my opinion, here's a list of steps that we, as Ruby and Python web developers, should follow:
So, as others already suggested, lay low for now and work on step (2) using Rails or Django. ;)
项目如何获得临界质量是一个神秘的过程。性感营销绝对有帮助。我认为 Ruby on Rails 的推出以及引人注目的截屏视频有助于其成功。该框架是由一家商店开发的，该商店还开发了人们想要使用的很酷的应用程序，这也有帮助。
当然，该框架还必须在技术上具有吸引力，RoR 就是如此。
正如其他评论者指出的那样，如果您想要一个被广泛采用的 Python 框架，Django 可能更适合您。或者也许您应该切换到 Ruby on Rails？
How projects gain critical mass is a mysterious process. Sexy marketing definitely helps. I think the fact that Ruby on Rails launched with a compelling screencast helped its success. It also helped that the framework was developed by a shop that also developed cool apps that people wanted to use.
Of course, the framework has to be technically appealing as well, which RoR is.
As other commenters have pointed out, Django may be a better fit for you if you want a Python framework with wide adoption. Or maybe you should just switch to Ruby on Rails?