ASP.net Webforms vs MVC
-
I was wondering what people favor, webforms or MVC?
-
We forms is considered very legacy. If you are doing something new use MVC.
MVC is the standard architecture for all web designs, not just .NET. You should have a pretty good technical reason to consider a different approach.
Look at Ruby, PHP and Python too rather than C#. Better cross platform options, less technical debt.
-
@scottalanmiller said:
We forms is considered very legacy. If you are doing something new use MVC.
MVC is the standard architecture for all web designs, not just .NET. You should have a pretty good technical reason to consider a different approach.
Look at Ruby, PHP and Python too rather than C#. Better cross platform options, less technical debt.
I just read another article about ASP.NET the TLDR was below. Do you are agree with something like this?
Microsoft’s ASP.NET is too restrictive and costs too much. Microsoft’s target audience builds products that are generally poorly written and lag 4-8 years behind the current platform version. Other open platforms can be used with little to no cost and lower overall cost of ownership.
-
Not 100%, but mostly. Microsoft MVC, for example, was only done through an open source effort and five years behind the industry. ASP.NET has never been a leader in web application development and is doing little to keep up. It's not bad and it is a viable choice if you are absolutely, 100% sure that you are tied to the Microsoft platform (for the server side, for hosting, etc.) for forever. But if you have ANY chance of being able to be non-Microsoft at all, you are shooting yourself in the foot.
ASP.NET is not a platform that I would consider if you are not a Fortune 100 with a dedicated software engineering department to support that stuff. Requires tons of extra money and technical resources to do the same things that you get with other platforms.
-
Microsoft's target audience is another issue. C#, F# and ASP.NET are decent products. F# especially. The .NET platform is deep and powerful. But the vast majority of Microsoft's development audience is those that are either 1) trapped and their management gives them no choice of language based on political reasons or 2) do so out of a mistaken belief that somehow Microsoft development tools are easier or 3) that because they use Microsoft somewhere that they have to use it everywhere.
Those three reasons, all which indicate bad things, are the driving forces behind choosing the Microsoft development technologies. There is a reason why huge companies and software engineering houses almost universally do not use them. Java for enterprise rather than .NET and other platforms for software houses are the norm.
-
For modern application development your first thoughts should always be Ruby, PHP and Python with JavaScript and a few others as possibilities but far less likely. As a non-dedicated software engineering team Ruby, PHP and Python should be your go to answers.
Of those, PHP is the easiest, Ruby the most powerful, Python the easiest to maintain and the fastest in performance.
