4 ms·

I'm a .NET dev by day and do a lot of Ruby/Rails/Sinatra by night. I would seem a natural target audience for NancyFX since I've enjoyed exploring both ends of

I'm a .NET dev by day and do a lot of Ruby/Rails/Sinatra by night. I would seem a natural target audience for NancyFX since I've enjoyed exploring both ends of the Ruby web framework world. But, I am resistant to invest much in NancyFX. I can't see where it fits in the enterprise world where most .NET devs live. With 4 choices already (WebForms, MVC, Web API, WCF) for developing sites/apps/services, I just don't have a good story for inserting Nancy into the mix. My primary goal, in developing for enterprise, after meeting customer requirements, is to build things that are simple to maintain and can be picked up easily by any other .NET developer. I loathe custom/in-house frameworks for that reason and while NancyFX has a strong community as far as I can tell, there's no guarantee that community won't tire and move along. I'll keep an eye on it, but for now, skipping over it.

cwbrandsma 14y ago
Devil's advocate here: WCF was never a real choice.
- jinushaun 14y ago
  Who even uses WCF? It's one of those MS technologies that even MS employees can't help but talk derisively about, like Sharepoint.
jinushaun 14y ago
I always have issue with the "enterprise" cop out that many .NET developers like to fall back on when attempting to explain their resistance to using non-MS libraries. It reminds me a lot of iPhone v Blackberry in "enterprise" and we all know who won that... At the end of the day, "enterprise" people go home and become "consumers". Google and Facebook aren't enterpise and serve billions of requests a day, but they are founded on OSS technology. What does enterprise besides expensive software with vendor lock-in? There is no guarantee that MS won't tire and move along either. At least with OSS like Nancy, you don't have to worry about MS sunsetting a product your company relies on. You can continue to develop it long after the project has died.

cwbrandsma 14y ago

Devil's advocate here: WCF was never a real choice.

jinushaun 14y ago
Who even uses WCF? It's one of those MS technologies that even MS employees can't help but talk derisively about, like Sharepoint.

jinushaun 14y ago

I always have issue with the "enterprise" cop out that many .NET developers like to fall back on when attempting to explain their resistance to using non-MS libraries. It reminds me a lot of iPhone v Blackberry in "enterprise" and we all know who won that... At the end of the day, "enterprise" people go home and become "consumers". Google and Facebook aren't enterpise and serve billions of requests a day, but they are founded on OSS technology. What does enterprise besides expensive software with vendor lock-in? There is no guarantee that MS won't tire and move along either. At least with OSS like Nancy, you don't have to worry about MS sunsetting a product your company relies on. You can continue to develop it long after the project has died.