If you're using it, you know, if you're not, you probably haven't updated yourself since ASP.NET was WebForms.
May 05, 2022
If you're using it, you know, if you're not, you probably haven't updated yourself since ASP.NET was WebForms.
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with ASP.NET
ASP.NET has come a long way since 2010 when I started my career in web development. It was a cumbersome and slow technology that was only used by "Microsoft shops" that has transformed into an easy-to-use and open source (!) technology that is also one of the fastest web app hosts in the world. The .NET Core team has really made ASP.NET shine.
We use it to build anything from small internally-used applications to large web applications that scale to thousands and thousands of users.
We use it to build anything from small internally-used applications to large web applications that scale to thousands and thousands of users.
- Build web applications with ease.
- Get up and running in minutes.
- Make it easier to vote on features that we want to see implemented.
- High-performance
- SignalR support
- Modularization
- Easy to scale
- Easier to develop re-usable packages.
NodeJS is a popular technology because, in my opinion, when it was introduced it made significant improvements on how easy it was to work with a familiar language (JS) on the server-side. But, now that it's no more a new technology and other competitors have caught up, I find little reason to use it. JS is terrible, even with Typescript. The benefits of a fast, strongly-typed language that receives constant updates like C# are just, too many. Not to mention that NodeJS, while fairly fast, makes it hard to scale with more things that need to be managed by the developer or devops.
Do you think ASP.NET delivers good value for the price?
Yes
Are you happy with ASP.NET's feature set?
Yes
Did ASP.NET live up to sales and marketing promises?
Yes
Did implementation of ASP.NET go as expected?
Yes
Would you buy ASP.NET again?
Yes