MVC4 would be excellent indeededly.

Agreed. The view system is indeed ready for an upgrade.

I wish I had more coding experience so I could contribute if there's a milestone set for that. I'm still a noob with MVC though.

No need to upgrade what works fine just because it's new and gives nothing except a pain in the ass.

Umbraco 5 comes to mind.

Can you explain what you mean MVC4 doesn't give you anything over web forms and explain how it's more difficult to maintain than web forms?

What view engines can be used with MVC4? 🙂

You mean like, Razor?

Agreed. I personally *really* like razor. But am fine with WebForms if it means code reuse. WebAPI or Simple.Web (http://blog.markrendle.net/2012/06/01/simple-web/ ) would be the way to go to convert the existing AJAX stuff to proper REST API stuff.

Stuff on my YAF.NET todo list:

1. Finish the plugin architecture -- this would help with design decisions going forward.

2. Minification

3. API

4. Open for discussion: Convert to Bootstrap CSS (with tons of existing themes) and Controls -- also less use of JQuery UI.

5. MVC design that would minimize use of web form pages and specifically logic in the web forms.

6. NuGet gallery for YAF.NET plugins and themes.

Not that I am asking you to explain yourself to me, but I would like to help somehow and if you could elaborate a little more on the items perhaps I could? I really love YAF and in anyway that I can help, I'd like to.

1. Plugin architecture for something like TapaTalk?
2. Minification? shrink lines of code?
3. API ... what would the intent/goal be?
4. I think from what you've said about Bootstrap, this would be HUGE for YAF.
5. My experience with MVC is that it's quite nice and very good for code reuse. Also, I think it might shorten up URL's too.
6. I no ziltch about nuget, I be useless here lol

Highly probably this is simply rewriting fast custom code into slow generic.

Anyway, there will be an alternative.