Just to throw in my 2 cents:

I decided for Blazor specifically because it uses mainly one language for coding, backend and frontend alike. That is the one thing I liked of VFP, to have one basic language with only some exceptions to be done differently.

Using Blazor I have to do minimal work in CSS if at all, very little JavaScript, but more than 90% C# backend and frontend alike. You do need some javascript/CSS framework though, there are some free ones and some more professional ones. For my simple project I used Blazorise (https://blazorise.com/)

If you are interested I could show you my project so you can make yourself a picture of it.

>Hello Michael,
>
>If you don't mind me asking,.
>
>Why did you decide to use Blazor?
>
>Recommandation?
>
>Just because the big Microsoft is behind it?
>
>Because of the programming language?
>
>When did you start using it? Is it evolving fast?
>
>I appreaciate all the comments.
>
>Regards
>
>>>And now here comes Blazor. I never really heard about it in the last weeks. But recently that changed.
>>>Comments?
>>
>>No experience with it yet.
>>I really really really want it to work.
>>Jumping between C# and JavaScript is a pain.
>>
>>We are using DevExpress components and their Blazor grid is in "preview" and not feature complete, so we are waiting.