Holy crap, you wrote what I was thinking, except I've done web development since 2000. I've ditched all other javascript frameworks and am now all Vue, all the time (with a little vanilla js thrown in when needed).
Coincidentally, I've built a .NET core web app as well, with Vue.js handling nearly the entire UI. It's lightening fast since I'm letting .NET handle the backend and Vue handle the frontend. I built the entire thing on my little Macbook Air. Hit me up if you want to talk shop sometime.
I'm sure the ruby, python, rust folks are snickering...but .NET Core + Vue.js is an A-List webdev stack as fas as I'm concerned.
What makes .NET core particularly notable in this pairing? I don't think any Ruby/Python/etc folks will be snickering, but if all we're talking about is a REST API (or similar) connecting to a Vue frontend then the idea is pretty backend agnostic.
I have written a few .NET Core web apps, some with React frontends and one with a Vue frontend.
I am using Blazor for the first time in a .NET Core 3 app and I don't think I can ever go back to a JS Framework. If you like Vue then give Blazor a try, it's similar component-wise except Razor components functions are C# instead of JavaScript.
Only downside is browser support as client-side Blazor is experimental and compiled to WebAssembly. Server-side Blazor streaming is GA though, and it is widly supported if your consumers generally have fast connections, such as Enterprise uses.
Coincidentally, I've built a .NET core web app as well, with Vue.js handling nearly the entire UI. It's lightening fast since I'm letting .NET handle the backend and Vue handle the frontend. I built the entire thing on my little Macbook Air. Hit me up if you want to talk shop sometime.
I'm sure the ruby, python, rust folks are snickering...but .NET Core + Vue.js is an A-List webdev stack as fas as I'm concerned.