ASP.NET Core is very straightforward and easy to work in. It's typically more performant than interpreted language frameworks, but it can be more verbose.
ASP.Net core is powerful but even with it being my day job I still wouldn’t recommend it for this niche.
* It’s damn complicated with a real learning curve to get your head around dependency injection, the vast standard library, heavy abstraction and Microsoft terminology. Day 1 basics can be easy but there’s a steep intermediate learning curve.
* ASP.Net has some nice plug and play stuff for generating Open API docs or logging for example but take a look at Laravel mentioned above and see how focused it is on making it easy to add features that the customer cares about.
* Documentation is expansive but not great, heavily focused on brand new user tutorials but terrible for quickly answering how do I do X? They struggle to stay up to date and i recall spending a good hour going down a rabbit hole because none of the tutorials were using the up do date magic spell to enable something.
* For pretty much everything you can think of there’s 3 ways to do it, good luck figuring out which one is the ‘correct’ way.
This may seem like a rant, I think ASP.Net Is good for a larger, more long term project where these annoyances are outweighed by performance and maintainability but I recently did a quick project in NextJS and the difference was night and day, despite it being my first ‘real’ project with the framework.
* It’s damn complicated with a real learning curve to get your head around dependency injection, the vast standard library, heavy abstraction and Microsoft terminology. Day 1 basics can be easy but there’s a steep intermediate learning curve.
* ASP.Net has some nice plug and play stuff for generating Open API docs or logging for example but take a look at Laravel mentioned above and see how focused it is on making it easy to add features that the customer cares about.
* Documentation is expansive but not great, heavily focused on brand new user tutorials but terrible for quickly answering how do I do X? They struggle to stay up to date and i recall spending a good hour going down a rabbit hole because none of the tutorials were using the up do date magic spell to enable something.
* For pretty much everything you can think of there’s 3 ways to do it, good luck figuring out which one is the ‘correct’ way.
This may seem like a rant, I think ASP.Net Is good for a larger, more long term project where these annoyances are outweighed by performance and maintainability but I recently did a quick project in NextJS and the difference was night and day, despite it being my first ‘real’ project with the framework.