3 ms·
MVC is actually pretty damn clunky. It has a lot of built-ins which are just frustrating (like IPrincipal, ugh). Also there are loads and loads of weird quirks
by mattmanser 14y ago
MVC is actually pretty damn clunky. It has a lot of built-ins which are just frustrating (like IPrincipal, ugh). Also there are loads and loads of weird quirks that pop up as soon as you start trying to do anything like returning JSON.
MVC was a huge step forward from the old ASP.Net, but it's still making a lot of frankly odd decisions or suddenly bizarre behaviours in the background (e.g. http://stackoverflow.com/questions/1975983/how-can-i-disable-http-keep-alive-in-asp-net-mvc http://stackoverflow.com/questions/1975983/how-can-i-disable...)
I think one of the reasons node.js is so great is that it just cuts out almost everything and gives you direct control over what is returned. MVC still mucks around with everything trying to be 'helpful' as it's really built on ASP.Net in the background.
To many of us, javascript is still one of the worst mainstream language around today.
Still, why not just make node.cs instead one wonders? Perhaps the existing ecosystem.
- ConstantineXVI 14y agoFWIW, I've found NancyFx[0] fairly non-clunky as far as .NET goes. It's more of an analogue for Sinatra than Node.js, though. [0] https://github.com/NancyFx/Nancy https://github.com/NancyFx/Nancy
- MatthewPhillips 14y agoAgreed, if you're forced to use C#, Nancy at least does it sanely (and RESTfully!).
- deleted 14y ago[deleted]
- tomkludy 14y agoI personally find those "helpful" things to be truly, well, helpful. For example the input validation, anti-forgery token validation, simple cache control, etc. Again, not saying you can't do these things in node. The two technologies can easily accomplish the same goal. But if your primary concern is avoiding JS, why would you choose a technology that is built entirely upon it? Node.cs might make more sense, I agree. I have a feeling the existing ecosystem might bring its own problems with the author's approach, because your C# code may have trouble integrating with those existing libraries, if the underlying generated code does not behave as the Javascript library expects.
- utnick 14y agocan you elaborate on the quirks around returning JSON with asp.net MVC? its a pretty common usecase.
- mattmanser 14y agoThere's a load of little things that are gotchas, but an example that pops into my head is that it wasn't compatible with default jQuery for example. If you didn't ask specifically for a content-type of application/json, which jQuery didn't by default, it would throw a hissy fit. It meant mucking around with the ajax object meaning you couldn't use certain jQuery shortcut methods. Regardless of what you 'told' MVC to do. So there's a bunch of things it's doing you're not even aware that it is nor have asked it to do. Think that was MVC 3? I've been using it since the first version, it's much better than it started (the original JSON support was awful), but you still every now and then get a WTF moment. For example I still really have no idea the 'right' way to return 404 or 500 error pages. I swear they change their mind every release.
- sequence7 14y agoBy default MVC 4 will return JSON so you don't need to specify the content-type unless you want something that isn't JSON.
- mattmanser 14y agoIt's not the return type, it was the request type. It didn't like if you requested it with plain/text instead of application/json. Which was jQuery's json method's default.
- sequence7 14y agoplain/text gives you JSON in MVC 4. I understood what you were saying, the default in MVC 4 is now to return JSON unless you specify otherwise.
- 14y ago
- jimbobimbo 14y agoWhat's wrong with IPrincipal, which btw is a .NET, not MVC thing?