Dangers of the new ASP.NET MVC framework(blog.madskristensen.dk)

submitted by simonechsimonech(10.1k) 4 years, 3 months ago

Will the new MVC framework split the ASP.NET community in 2? One following the "stardard" WebForm paradigma and one following the more "strict" approach?

4 comments |category: |Views: 11

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

posted by mrkurtmrkurt(280) 4 years, 3 months ago 0

The "great divide" already exists. What's new is a toolkit from Microsoft that caters to the other side, so to speak.

Reply

posted by davidsdavids(480) 4 years, 3 months ago 0

Good article. At the end of the day however, there is nothing that says you HAVE to use the MVC model - until and unless they force it upon the asp.net framework.

Reply

posted by atifazizatifaziz(1000) 4 years, 3 months ago 0

Yep, this kind of "great divide" has existed in the C/C++ world for a long time and it sorted itself out alright even if it was annoying at time. Anyone remember Windows through the lens of the straight C API versus MFC versus ATL and WTL? Hey, what do we call those programmers today anyhow? "Unmanaged" programmers? Sorry, couldn't resist. :)

Reply

posted by jburgerjburger(815) 4 years, 3 months ago 0

I'm not sure it's a "danger" at all. Even if a such divide is created, each side will become a thriving community in its own right.

It happens all the time. People grow apart, find new things, new friends, new frameworks...

Reply

information Login or create an account to comment on this story