ASP.NET MVC 和 FubuMVC 之间的主要区别是什么？
我认识的一位开发人员刚刚向我展示了 FubuMVC，并且有一些问题我们是否应该尝试使用它无论是否在真实的项目中。 到目前为止，当前的设计选择是 ASP.NET MVC。
我感兴趣的是：
ASP.NET MVC 和 FubuMVC 之间的核心区别是什么？
任一框架的收益/损失是什么？
FubuMVC 准备好迎接黄金时段了吗？
您会在新项目中使用这两个中的哪一个？
A developer I know just showed me FubuMVC and there was some question whether or not we should attempt to use it on a real live project or not. The current design choice so far has been ASP.NET MVC.
What I'm interested in finding out is:
What are the core differences between ASP.NET MVC and FubuMVC?
What are the gains/loses with either framework?
Is FubuMVC ready for prime time?
Which of these two would you use on a new project?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
看来主要区别在于 FubuMVC 实现了 Front Controller 模式。
如果 ASP.NET MVC 还没有准备好迎接黄金时期（它还处于 Beta 阶段），我怀疑 FubuMVC 是否已经准备好，因为它是前者的一个分支。
FubuMVC 背后的人非常优秀，Chad Myers 和 Jeremy D. Miller 在社区中非常受尊敬，也是 ALT.NET 非常活跃的成员。 但菲尔·哈克 (Phill Haack)、斯科特·汉塞尔曼 (Scott Hanselman) 也是如此。 Co，ASP.NET MVC 背后的人。
如果您只是想开始，我会推荐 ASP.NET MVC，因为它背后有更多的人员和资源，如果您不喜欢所看到的内容，请选择 Fubu。
It seems that the main difference is that FubuMVC implements the Front Controller pattern.
If ASP.NET MVC is not ready for prime time yet (it's in Beta), I would doubt that FubuMVC would be ready, since it's kind of a fork from the former.
The guys behind FubuMVC are quite good though, Chad Myers and Jeremy D. Miller are very respected among the community and very active members of ALT.NET. But so is Phill Haack, Scott Hanselman& Co, the guys behind ASP.NET MVC.
If you just want to get started I would recommend ASP.NET MVC because it has more people and resources behind it, and go for Fubu if you don't like what you see.
我没用过Fubu Mvc，只是看了看。 它尚未完成，但我可能会用它来部分重写现有的非 Web winforms 项目。 Asp.Net Mvc 仅适用于 Web 项目。
I haven't used Fubu Mvc but just looked at it. It's not finished but I might use it on partially rewriting an existing non-web winforms project. Asp.Net Mvc is for web projects only.
1 月 13 日的播客链接 FubuMVC 上的 Herding Code
Podcast link from Jan 13th Herding Code on FubuMVC
@maz 这取决于你的应用程序要做什么、它的时间范围、它的重要性等等。
首先，我鼓励你把两者都搞乱。 总体而言，两者并不比另一个更好或更差，它们是不同的，并且每个都有您应该考虑的显着优点和缺点。
至此，ASP.NET MVC 更加成熟，并拥有更多的测试人员和眼球。 因此，如果您正在做任何类型的严肃项目（即您会为此获得报酬），我会鼓励您在此时使用 ASP.NET MVC，因为它将更快“发布”并获得更多支持。
（更新 [2011 年 2 月 26 日]）：FubuMVC 现在被多家公司和团队用于成熟的生产应用程序，这些应用程序已经发布了多个基于 FubuMVC 的主要版本。 虽然文档仍然有些缺乏，但框架的质量现在已经确立为具有生产价值）
如果您正在开始一个爱好项目（即个人博客、个人/家庭相册等），那么我会邀请您选择 FubuMVC 并开始使用它。 请记住，这一点基本上是我、杰里米和其他一些人的爱好，因此无法保证时间表等。它还没有真正公开宣布（无论好坏，它都已经泄露了），所以还没有'目前还没有大量的捐款。 我希望随着它的成熟，我们达到第一个里程碑，然后向全世界宣布，贡献将会增加。
最后，使用其中任何一种都可能会鼓励更好的开发实践，例如 ASP.NET WebForms，并且熟悉其中一种将使您更容易、更快地掌握另一种。
这实际上取决于您正在从事的项目的重要性，因此请负责任地选择。
@maz It depends what your application is going to do, its timeframe, its criticality, etc.
First, I'd encourage you to mess around with both. Neither is better or worse than the other overall, they are different and each have significant strengths and weaknesses that you should consider.
At this point, ASP.NET MVC is more mature and has had more testers and eyeballs looking at it. So if you are doing any sort of serious project (i.e. you're getting paid for it), I would encourage you, at this point, to use ASP.NET MVC as it's going to "ship" sooner and be more supported.
(UPDATE [26 Feb 2011]): FubuMVC is now being used by several companies and teams in mature, production apps that have had several major released versions based on FubuMVC. While the documentation is still lacking somewhat, the quality of the framework is now well established as production-worthy)
If you're starting a hobby project (i.e. personal blog, personal/family photo album, etc) then I'd invite you to pick up FubuMVC and start playing with it. Keep in mind that this point it's basically a hobby of mine, Jeremy's, and a few others so there's no guarantees on timeline, etc. It hasn't really been publicly announced (it's leaked out, for better or worse) so there hasn't been a flood of contributions yet. I'm hoping as it matures and we get to the first milestone then announce it to the wide, wide world, contributions will ramp up.
In the end, using either will likely encourage better development practices over, say, ASP.NET WebForms and getting familiar with the one will make it easier for you to pick up the other one rather quickly.
It really comes down to the criticality of the project you're working on, so choose responsibly.