Microsoft launches new app store for Windows – from React to Shoelace, Lit, Vite
theverge.com
theverge.com
Unless it has changed, I think GCP uses it, as do many internal dashboards.
I love .NET and ASP.NET Core, but I use it purely for backend. And even there, I use 3rd party libraries like Fast Endpoints (https://fast-endpoints.com/). Microsoft keeps bringing in new technologies and effectively abandoning the ones that fall out of favour (look at the progression from MVC -> Razor Pages -> Blazor). I do not blame the Microsoft Store team for not trusting the .NET team to not simply abandon Blazor as well somewhere down the line and instead opt for other technologies for the front-end.
I really don't know how to make out of it.
It started by being .NET for WebAssembly, and then it took a life of its own, with the team pushing it everywhere there is a Webview, as if the GUI civil war going on Redmond wasn't already bad enough.
Since WebForms was a victim of the "Python 2 / Python 3" like reboot of the .NET ecosystem, at very least Blazor provides a similar development experience for those folks.
For the rest of us, used to clean MVC approaches, without allergy to JavaScript, mostly working in mixed FE/BE teams, Blazor is a solution looking for a problem, not worth the additional amount of complexity layers between browser and applications.
Web Forms and JSF have taught me not to go there again.
.NET nowadays seems to be mostly used in the backend (at Microsoft).
Notice how much of the .NET Core development seems to be driven by ASP.NET architects.
Besides the GUI chaos, they hardly do any feature comparison with other GUI frameworks, like they happen to do with every single cloud ecosystem out there.
And Shoelace is the same: one of the best UI frameworks out there.
The frontend landscape actually changed way less than the backend in the past 10 years.
React is 10 years old, Angular is older and Vue is around 10 years, too.
Now to the backend, how many frameworks are out there? First you have multiple cloud providers each with their own set of preferred services.
Then you have the old frameworks like Rails, Django, PHP (wordpress, symfony, laravel), which changed a bit less, just like frontend but they are just a % of the backend. There are also the corporate backends like Spring and many more, which although they are still running and stable, 10 years ago Java was the obvious choice for most if not all enterprise projects but not anymore.
Then you also have multiple backend providers like supabase, firebase.
React is the aberrant abstraction that layered a really broken MVC-ish layer on web front ends.
It works through standard custom elements (not Yet Another Protocol), which brings quite a lot of advantages (less coupling, interoperability, etc.) while also providing helpful utilities for creating and managing instances of custom elements. Lit is... well, lit.