A thing that’s holding .NET in a big way among non-corporate developers is that there’s no good self hosting story.
It’s Azure or “you’re on your own pal!”, basically.
Compare this with PHP/LAMP-stack that allowed for cheap, fun experiments with small side projects which resulted in a couple of pretty significant companies.
@Paxxi oh, no question. But imagine if Microsoft built a Netlify/Firebase-like service, where they abstract away all the myriad of choices and basically said “give us your GitHub repo url and we’ll give you a url to a running app”
Every few months, I come back to rewriting a #todo app in #aspnetcore, sometimes it's with Blazor, sometimes it's Razor Pages, and this time with #Htmx (although I may have already done HTMX 😅)
I got some quality-of-life improvement issues entered to help make #JetBrainsRider better, too. So that's a win!
Usssh, now I’ve done it. I actually have to talk about htmx and blazor next monday. So I need all you folks help, what are the libraries you are using? What are the good and bad things about that combo?
I’ll repeat it. #aspnetcore should cater harder to the web designer community with static site generation, razor build steps for prerendering JS/Web components, and more JS build-tool integration.
It's a missed opportunity for #dotnet as these folks use their talents elsewhere.
Seriously who had the idea to call Blazor components “razor components” where you also have razor pages and razor templates that are not Blazor.
This is so confusing, just call them Blazor components. #dotnet#razor#blazor
