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?
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.
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.
@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.
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.