undefined | Better HN

0 pointsNicoJuicy11y ago0 comments

I actually haven't met anyone who thought like you.

WebApi feels great and respects the HTTP spec (PUT, DELETE, UPDATE, POST,GET) and even the OData spec is compliant and after all, it's very fast to implement WebAPI and OData.

The .Net (mostly Asp.Net) is evolving fast for technologies like SignalR en OWIN.. And actually that's great.

You could still use webforms if you want, but i woudn't recommend that.

Most people hate change, but considering the (positive[subjective]) changes, they have done.. I think it's awesome and liberating.

OWIN has a improved authentication implementation, which has been a long requested feature for Asp.Net. For example, when you wanted to customize the Authentication implementation (don't remember the interface), you had to implement all of the methods (ForgetPass, EmailPass, ...). OWIN fixes that also (which was hard because of their former implementation)!

The only way it seems like more hassle/mess, is because there are more DLL's being imported, but i don't care because i know the reason behind it :)

0 comments

mattmanser11y ago

I think you fundamentally misunderstood me, I'm not against change.

I love MVC. Webforms is a complete travesty anyone still using it for new projects is mad. I never understood why Scott Gu defended it, it's a bad choice in the modern world.

I do not love where they're taking it though, which is to a place of no choice and bad design decisions.

REST is a bad design decision in my opinion. If you love it, fine, but don't force me to have only 4 methods on my classes. Strict REST doesn't make sense to me, it never has and never will. Most of the APIs I love using don't follow strict REST designs in their APIs and in my opinion those APIs are much better than the ones that do.

Knockout.js is a bad design decision. Use it if you want. But it shouldn't start adding a load of cruft in my project every time I click 'Add View...' though.

NicoJuicyOP11y ago

I do not understand why you don't like REST ? It's been designed with the HTTP protocol simultaneously and it's how you should develop things for an API : http://en.wikipedia.org/wiki/Representational_state_transfer...

You are not limited to 4 methods, there are only 4 methods of altering data (eg. CRUD (create, read, update and delete))? Recently, they introduced batch support (i could have used that 3 months ago though :P)

Errors? Return a standard HTTP Code :)

Knockout is optional, it's a template to start with. Want to do it yourself? Create an empty project, use one on Github/Codeplex, import an extensions with custom scaffolders (mvc scaffold) or go and create your own with T4 templates, i have done it myselve thanks to some info on Scott Hanselman's blog: http://www.hanselman.com/blog/ModifyingTheDefaultCodeGenerat...

PS. Kinda curious which API's you are referring to?

j / k navigate · click thread line to collapse