有 h ttp://book.merbist.com/ 和 h ttp://wiki.merbivore.com/，但两者都非常不完整，而且经常过时。 h ttp://www.merbivore.com/documentation/current/doc/rdoc/stack/index.html 有自动生成的 API 文档，但这些文档也非常不完整（大多数方法的文档都非常不完整或不存在）例如，列出选项哈希中可用的选项。）关于各种 Merb 功能的博客文章有大量，但绝大多数都已经过时了，不再适用于当前的 Merb。
Tough call, but I'd start with Merb. Rails 3 will be Merb 2. The Merb core guys are taking over Rails development to make it more Merb-like (h ttp://yehudakatz.com/ et al.).
The drawback is that Merb is a moving target and documentation is somewhat lacking, whereas Rails has extensive beginner's documentation available.
There are h ttp://book.merbist.com/ and h ttp://wiki.merbivore.com/, but both are very incomplete and not infrequently out of date. There are the autogenerated API docs at h ttp://www.merbivore.com/documentation/current/doc/rdoc/stack/index.html , but those are also horrendously incomplete (most methods have grossly incomplete or nonexistent documentation that doesn't, for example, list what options are available in an options hash.) There are tons of blog posts on various Merb features, but the vast majority are horrendously out of date and no longer applicable to current Merb.
If you do go with Merb, resign yourself to spending hours reading the (minimally commented) test suite and source code yourself to figure out how to get things done. (You'll get a deeper understanding of the library that way anyway, at the cost of some upfront screen time reading code.)
Rails, by contrast, is a relatively stable target with extensive tutorials and documentation, but it's all going to be obsolete in Rails 3 when it's Merbified. You'll have to learn Merb anyway at that point, rendering all your work learning classic Rails useless. So I'd go with Merb from the outset.
(sorry about the lack of hyperlinks, but "new users can only post a maximum of one hyperlink")
发布评论
评论（4）
从 Rails 开始，因为：
Rails 是 Ruby 上最流行的 Web 框架，也是过去几年最流行的框架之一。
此外，Merb 正在与 RAILS 合并：
http://yehudakatz.com/2008/12/23/rails -and-merb-merge/
所以你最好从 Rails 开始：
http://rubyonrails.org/download
Start with rails because:
Rails is the most popular web framework on Ruby, and one of the most popular frameworks of the past years.
Also Merb is merging with RAILS:
http://yehudakatz.com/2008/12/23/rails-and-merb-merge/
So you are better off starting with Rails:
http://rubyonrails.org/download
Sinatra 是另一个 Ruby Web 框架。我听说它更适合较小尺寸的应用程序。
Sinatra is another Ruby web framework. I've heard that it's geared more towards smaller size applications.
艰难的决定，但我会从 Merb 开始。 Rails 3 将是 Merb 2。Merb 核心人员正在接管 Rails 开发，使其更像 Merb（h ttp://yehudakatz.com/ 等）。
缺点是 Merb 是一个移动目标，并且文档有些缺乏，而 Rails 有大量的初学者文档可用。
有 h ttp://book.merbist.com/ 和 h ttp://wiki.merbivore.com/，但两者都非常不完整，而且经常过时。 h ttp://www.merbivore.com/documentation/current/doc/rdoc/stack/index.html 有自动生成的 API 文档，但这些文档也非常不完整（大多数方法的文档都非常不完整或不存在）例如，列出选项哈希中可用的选项。）关于各种 Merb 功能的博客文章有大量，但绝大多数都已经过时了，不再适用于当前的 Merb。
如果您确实选择 Merb，那么您就得花几个小时自己阅读（注释最少的）测试套件和源代码来弄清楚如何完成工作。 （无论如何，您都会以这种方式更深入地了解该库，但代价是需要花费一些前期屏幕时间阅读代码。）
相比之下，Rails 是一个相对稳定的目标，拥有大量教程和文档，但它都将过时在 Rails 3 中，当它是 Merbified 时。无论如何，到那时你都必须学习 Merb，这会让你学习经典 Rails 的所有工作变得毫无用处。所以我从一开始就选择 Merb。
（很抱歉没有超链接，但是“新用户最多只能发布一个超链接”）
Tough call, but I'd start with Merb. Rails 3 will be Merb 2. The Merb core guys are taking over Rails development to make it more Merb-like (h ttp://yehudakatz.com/ et al.).
The drawback is that Merb is a moving target and documentation is somewhat lacking, whereas Rails has extensive beginner's documentation available.
There are h ttp://book.merbist.com/ and h ttp://wiki.merbivore.com/, but both are very incomplete and not infrequently out of date. There are the autogenerated API docs at h ttp://www.merbivore.com/documentation/current/doc/rdoc/stack/index.html , but those are also horrendously incomplete (most methods have grossly incomplete or nonexistent documentation that doesn't, for example, list what options are available in an options hash.) There are tons of blog posts on various Merb features, but the vast majority are horrendously out of date and no longer applicable to current Merb.
If you do go with Merb, resign yourself to spending hours reading the (minimally commented) test suite and source code yourself to figure out how to get things done. (You'll get a deeper understanding of the library that way anyway, at the cost of some upfront screen time reading code.)
Rails, by contrast, is a relatively stable target with extensive tutorials and documentation, but it's all going to be obsolete in Rails 3 when it's Merbified. You'll have to learn Merb anyway at that point, rendering all your work learning classic Rails useless. So I'd go with Merb from the outset.
(sorry about the lack of hyperlinks, but "new users can only post a maximum of one hyperlink")
从 Rails 开始...有传言 merb 将被同化 http://weblog.rubyonrails.org/2008/12/23/merb-gets-merged-into-rails-3
Start with Rails ... rumor has it merb will be assimilated http://weblog.rubyonrails.org/2008/12/23/merb-gets-merged-into-rails-3