5 ms·
After looking for enough time, it may be worth it to make some compromises, pick one and try building your application with it. You may never find “the” framew
by jcpst 4y ago
After looking for enough time, it may be worth it to make some compromises, pick one and try building your application with it.
You may never find “the” framework.
Lately my default has been AspNet Core and C# (or F# if I’m feeling frisky). Not because it’s the ultimate framework for me (although it _is_ very good), but it’s what I learned, thanks to learning on the job.
I remain a microsoft skeptic though. I continue to dabble in other tooling just in case they lock down the framework or tools in the future. I like django, for example.
- JaFu0815 4y agoI am in a similar situation. I have written most backends in AspNet Core, mostly because C# is usually my go-to language. I have looked into Blazor a bit. There are some aspects it does well and writing frontend in C# is very appealing to me, however, the way of datafetching is not the most elegant, as far as I have seen and can judge.
- jcpst 4y agoI’ve been using razor pages. For me it takes the abstractions I enjoyed with aspnet MVC, with less of the boilerplate- controllers, etc