The power of Custom Model Binding in ASP.NET MVC(dotnetcurry.com)
dotnetcurry.com
The power of Custom Model Binding in ASP.NET MVC
http://www.dotnetcurry.com/ShowArticle.aspx?ID=584
1 comments
This is to software developers what Katrina was to New Orleans: tragic, embarrassing and in many ways preventable.
What's really scary is that 372 people liked it on Facebook and 2 users rated it 3 out of 5 stars.
Having said that, I like the idea of mapping URLs to method invocations on persistent objects. Zope does that since about 1998.
And that makes me think. I never liked C++ (and it took me years to command the will to learn it) after being introduced to OOP with Smalltalk. The same way, I could never like Hybernate, EJBs and stuff like that because I was introduced to Zope before ever touching them.
Having said that, I like the idea of mapping URLs to method invocations on persistent objects. Zope does that since about 1998.
And that makes me think. I never liked C++ (and it took me years to command the will to learn it) after being introduced to OOP with Smalltalk. The same way, I could never like Hybernate, EJBs and stuff like that because I was introduced to Zope before ever touching them.
I'm genuinely curious if you're referring to MVC's model binders in general or just this specific article/solution? If it is indeed model binders as a whole, would you mind elaborating?
Care to explain?
I'll take a crack at it, whether you consider it satisfying is not something I can control.
I used every version of Visual Basic from 1 to 6 (and used 3 onwards for client work) alongside classic ASP 3 for web stuff. I did this well enough that I have a Microsoft MVP certificate hanging in the bathroom here at Unspace.
When they pushed .NET down our throats (I was one of the 200 MVPs that signed a petition demanding a COM-based VB7) I realized that culturally, MS tech was no longer a good fit for me and I looked for other options.
The thing I want to emphasize, though, is that during that 14 years I truly believed that VB, ASP, COM and Windows in general were great, powerful environments to build things in. I would argue that it was silly to suggest that PHP could do anything that ASP couldn't do. I believed this, and so did thousands of others on the forums I read at the time.
When I look back on MSFT dev communities today I see them 5-8 years behind on things like MVC frameworks, object mappers and new tech like MongoDB or OAuth or even REST in general.
The issues are not related to intelligence or integrity, but a generally conservative community that is told what to be excited about. I love the open source world because the pace of innovation is some exponential value faster than what I enjoyed for the first 2/3 of my career. It makes me feel passionately angry when I see people writing dozens of lines of code to do things that some frameworks make obvious and simple.
All generalizations, but still a very significant reality for me. Sometimes we're wrong about our tools, and there are simply better ways to do things.
I used every version of Visual Basic from 1 to 6 (and used 3 onwards for client work) alongside classic ASP 3 for web stuff. I did this well enough that I have a Microsoft MVP certificate hanging in the bathroom here at Unspace.
When they pushed .NET down our throats (I was one of the 200 MVPs that signed a petition demanding a COM-based VB7) I realized that culturally, MS tech was no longer a good fit for me and I looked for other options.
The thing I want to emphasize, though, is that during that 14 years I truly believed that VB, ASP, COM and Windows in general were great, powerful environments to build things in. I would argue that it was silly to suggest that PHP could do anything that ASP couldn't do. I believed this, and so did thousands of others on the forums I read at the time.
When I look back on MSFT dev communities today I see them 5-8 years behind on things like MVC frameworks, object mappers and new tech like MongoDB or OAuth or even REST in general.
The issues are not related to intelligence or integrity, but a generally conservative community that is told what to be excited about. I love the open source world because the pace of innovation is some exponential value faster than what I enjoyed for the first 2/3 of my career. It makes me feel passionately angry when I see people writing dozens of lines of code to do things that some frameworks make obvious and simple.
All generalizations, but still a very significant reality for me. Sometimes we're wrong about our tools, and there are simply better ways to do things.
The original comment author is clearly a well accomplished developer who has clearly understood every aspect of the given scenario and has thus told us - this is M$ technology, thus, it sucks. We should be using $deity_web_framework instead.
Things like strongly binding data to objects, thereby reducing load significantly is embarrassing and tragic. Real developers should do it the old fashioned way - make a model class, write forms, data mappers, sanitizers and validators by hand - who cares if you have to change it in four places whenever you need to add a new field, atleast you're not doing it the M$ way.
Things like strongly binding data to objects, thereby reducing load significantly is embarrassing and tragic. Real developers should do it the old fashioned way - make a model class, write forms, data mappers, sanitizers and validators by hand - who cares if you have to change it in four places whenever you need to add a new field, atleast you're not doing it the M$ way.
This is to comments what the Fox network is to news: hyperbolic, uninformative and yet bizarrely popular