3 ms·
I transitioned from Node to dotnet for backend last year and it's been great for APIs. Love C#. Performance is fantastic. The framework and tooling are very ma
by pier25 1y ago
I transitioned from Node to dotnet for backend last year and it's been great for APIs.
Love C#. Performance is fantastic. The framework and tooling are very mature (with exceptions like hot reload ugh). Entity Framework is amazing, by far the best ORM I've ever used.
I don't feel like an expert by any means but I'm productive. Some days I do hit some stuff that takes me longer that I would've hoped but I've been able to solve everything I've faced.
I only use it for APIs though. The fullstack stuff is not great. Maybe if Microsoft improved hot-reload I would consider Razor with a Vite setup. Blazor is just useless for me. It's very cool from a technical standpoint but your frontend is 10x slower and more bloated than the worst JS solution you can think of.
I connect my JS frontend layer with OpenAPI[1]. It's been ok but the whole OpenAPI experience is not as smooth as I had hoped.
[1] https://openapi-ts.dev/ https://openapi-ts.dev/
- kasajian 1y agoAre you experiencing any perf issues when using "Blazor Server"?
- pier25 1y agoI benchmarked rendering performance with Razor Pages and it was fantastic. I'm assuming Blazor Server is probably good too as long as you're not using the wasm stuff. The dx on the other hand... (just realized in my previous comment I didn't specify I meant Blazor with WASM)