I think YAF is essentially a hobby for the guys who are developing it, so the chances of them changing to different (cooler) technology is much higher than products that have commercial realities to deal with. Buyer beware I guess.
On Fri, Feb 1, 2013 at 1:35 PM, Katherine Moss <[email protected]>wrote: > Yes, WebAPI is wrapped inside of MVC4. And there’s another thing that > just makes me mad; when people want to rewrite their application for the > heck of it just so that they can be deployed under the latest fad. The > folks from Yet Another Forum are now saying that their project could be > moved and rewritten as ASP.net MVC too, and for what? To look cool? > Apparently, and what’s wrong with a project that is written in Web Forms > and doing fine? I’m sorry, but I don’t get it. And once that changes, if > it does, other folks who use YAF will be screwed including those at > Sueetie, who make a great product all based on Web Forms. Though web forms > and MVC can work together, though it’s not as simple as one would think. > If you want MVC, then use Web Forms MVP. And who said WCF is pointless > middleware? Isn’t it a good way to create web services? And if not for > WCF, what’s next? Back to ASMX from 2006? Come on! Anyway, guys, I’m > sorry for the rant, but I had to get it out somewhere, right? **** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Greg Keogh > *Sent:* Thursday, January 31, 2013 7:50 PM > *To:* ozDotNet > *Subject:* Re: New Web API project**** > > ** ** > > Thanks, glad to know I'm not alone, that link looks sensible and will save > a lot of suffering -- Greg **** >
