Skip to main content
Software Engineering

Return to Answer

Replaced poor choice of words; improved grammar
Source Link
WynandB
WynandB
  • 101
  • 4

Well, web formsWebForms have more learning resources available (simply due to the fact that it's older) and thus new programmers that aren't "In"in the know" will be more likely to find information regarding this older technology as opposed to the newer stuff like MVC.

Senior/experienced programmers are older and will be more proficient in the older technology due to the fact that they've programmed in it longer than they have in the newer one.

Unless you can spend the money and effort to get your guys as proficient in MVC as they are in web formWebForms applications, youryou're undoubtedly going to try and hold off upgrading to the new platform for as long as possible.

So it presents several logistical problemproblems: Do the benefits of MVC outweigh the it's cost in terms of lesser quality and deployment time? If I have a site written entirely in webformsWebForms, would it be worth the effort and money to integrate MVC into it?

As stated by a previous commenter, MVC also prevents you from achieving the same level of interface with the controller as you would be able to with web formsWebForms. While I'm all for the "Keep the user from fucking shitstuffing things up/learning" side of things, it can still be unreasonableunreasonably troublesome for teams to deploy/implement a program that fanatically sticks to that paradigm for everything they write.

Well, web forms have more learning resources available (simply due to the fact that it's older) and thus new programmers that aren't "In the know" will be more likely to find information regarding this older technology as opposed to the newer stuff like MVC.

Senior/experienced programmers are older and will be more proficient in the older technology due to the fact that they've programmed in it longer than they have the newer one.

Unless you can spend the money and effort to get your guys as proficient in MVC as they are in web form applications, your undoubtedly going to try and hold off upgrading to the new platform for as long as possible.

So it presents several logistical problem: Do the benefits of MVC outweigh the it's cost in terms of lesser quality and deployment time? If I have a site written entirely in webforms, would it be worth the effort and money to integrate MVC into it?

As stated by a previous commenter, MVC also prevents you from achieving the same level of interface with the controller as you would be able to with web forms. While I'm all for the "Keep the user from fucking shit up/learning" side of things, it can still be unreasonable troublesome for teams to deploy/implement a program that fanatically sticks to that paradigm for everything they write.

Well, WebForms have more learning resources available (simply due to the fact that it's older) and thus new programmers that aren't "in the know" will be more likely to find information regarding this older technology as opposed to the newer stuff like MVC.

Senior/experienced programmers are older and will be more proficient in the older technology due to the fact that they've programmed in it longer than they have in the newer one.

Unless you can spend the money and effort to get your guys as proficient in MVC as they are in WebForms applications, you're undoubtedly going to try and hold off upgrading to the new platform for as long as possible.

So it presents several logistical problems: Do the benefits of MVC outweigh the cost in terms of lesser quality and deployment time? If I have a site written entirely in WebForms, would it be worth the effort and money to integrate MVC into it?

As stated by a previous commenter, MVC also prevents you from achieving the same level of interface with the controller as you would be able to with WebForms. While I'm all for the "Keep the user from stuffing things up/learning" side of things, it can still be unreasonably troublesome for teams to deploy/implement a program that fanatically sticks to that paradigm for everything they write.

Post Made Community Wiki by Steve
Source Link
user32288
user32288

Well, web forms have more learning resources available (simply due to the fact that it's older) and thus new programmers that aren't "In the know" will be more likely to find information regarding this older technology as opposed to the newer stuff like MVC.

Senior/experienced programmers are older and will be more proficient in the older technology due to the fact that they've programmed in it longer than they have the newer one.

Unless you can spend the money and effort to get your guys as proficient in MVC as they are in web form applications, your undoubtedly going to try and hold off upgrading to the new platform for as long as possible.

So it presents several logistical problem: Do the benefits of MVC outweigh the it's cost in terms of lesser quality and deployment time? If I have a site written entirely in webforms, would it be worth the effort and money to integrate MVC into it?

As stated by a previous commenter, MVC also prevents you from achieving the same level of interface with the controller as you would be able to with web forms. While I'm all for the "Keep the user from fucking shit up/learning" side of things, it can still be unreasonable troublesome for teams to deploy/implement a program that fanatically sticks to that paradigm for everything they write.