I’ll be blunt, you don’t know how to use .NET core and you never learned, despite your claimed “several months” of use. > There are no tutorials on how to add

I’ll be blunt, you don’t know how to use .NET core and you never learned, despite your claimed “several months” of use. > There are no tutorials on how to add Vuejs or React to your asp.net core project. This is a remarkable complaint to make. There are literally template starter projects for react/angular when you go to file -> new project. If you choose not to use a starter template, adding your own frontend is trivial: place the built frontend in wwwroot and have an MVC endpoint that returns index.html. I’m not sure how this could be any easier, and it makes me wonder if you ever used .NET core at all. > Postgres is simply treated as "not important" and you are expected to use mssql. PostGres + Entity Framework Core is mostly a hack. You run into soo many issues that you'll be forced to leave Postgres and go for mssql. This is simply false. I have used Postgres with .NET core extensively and have never been forced to fall back on SQL server. Exactly what are these serious issues? > Only tutorials available teach basic stuff like middleware, rest api without authentication. Are you complaining about setting up authentication? It is easy to add JWT support in startup.cs and then secure endpoints via attributes. > You end up dealing with ugly DbContext for setting up basic models. And DbSets to enable tables for your models. All this ugly stuff is thrown in your face. What’s ugly about it? The DbContext represents a particular database connection and a DbSet represents an entity within that database. That’s an entirely rational way to represent the data layer. > Need image processing libaries? Good luck with that. There is simply no support. Another remarkable complaint to make. Nothing apart from OpenCV, ImageSharp, the native System.Drawing package, and this entire list of options: https://blogs.msdn.microsoft.com/dotnet/2017/01/19/net-core-image-processing/ https://blogs.msdn.microsoft.com/dotnet/2017/01/19/net-core-... You should really stop making claims about .NET core that are demonstrably false.