Svelte VS awesome-blazor

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.

Volar originally was Vue3's language support tool for VScode (I don't know about other editors). By today, volar has become a language indipendent framework to create language tools. It might still be a bit early for the dev with skill issues like me to use it and build some tools, but astro and svelte already use Volar to create their language tools.

The thought that came to mind was to use a front-end framework or library like React or Svelte.

Since I don’t know what theme constraints you might have, I’d check out this and go to the ‘Component Bundles’ section under ‘Libraries and Extensions’. There are some good open source component libraries that should offer at least one good date picker alternative that you could drop in for the licensed one causing you issues.

Querying a (MySQL) database can be done in multiple ways in .NET, I usually prefer to use Entity Framework Core. For components, I like to use the MudBlazor component library. It also has an autocomplete component. If you want to look at different options for Blazor libraries/components(and more) you can take a look at this awesome collection.

Anyhow, there are a few similar sites at https://blazorschool.com/ and https://blazor-university.com/ , and if you're serious about it there are a ton of resources catalogued at https://github.com/AdrienTorris/awesome-blazor

https://github.com/AdrienTorris/awesome-blazor, specifically under the Libraries & Extensions section.

It is usually true that Microsoft's documentation falls behind their implementations, but it does eventually catch up. But this: https://docs.microsoft.com/en-us/aspnet/core/blazor/?view=aspnetcore-6.0 isn't all that bad. There are a lot of resources here https://github.com/AdrienTorris/awesome-blazor too.