> I've never built anything on .Net The grass isn't greener. I've built in both - I have a .NET Core/Angular SaaS app that I created and sell, and I've been bu

> I've never built anything on .Net The grass isn't greener. I've built in both - I have a .NET Core/Angular SaaS app that I created and sell, and I've been building greenfield in Next. I much prefer Next. The duplication in .NET/Angular has never been worth it...not once. And having network calls for everything is unnecessarily painful. I started the app in 2019, when RESTful SPAs were all the rage. I bought into the hype that you should have API endpoints for everything no matter what, because you'd soon have a mobile app and daemons and this and that. Turns out, YAGNI. It would've been better to server-side render and only create API endpoints when necessary. That's what I like about Next: Static generate where you can, server-side render per request where you can't, SPA where necessary - and the layers are as flat as can be. It's the best of all worlds. That being said, I've worked in .NET for ~16 years now, and I like it more than JavaScript/TypeScript. But I'd still rather develop a web app in Next and put any background services elsewhere in .NET if needed.