4 ms·
Its a shame that this does not have Blazor components.
by kumarvvr 3y ago
Its a shame that this does not have Blazor components.
- Semaphor 3y agoAgreed, especially as the old Fluent UI Blazor components [0] were the only ones in my testing without atrocious performance. [0]: https://www.fluentui-blazor.net/ https://www.fluentui-blazor.net/
- RadiozRadioz 3y ago> without atrocious performance I don't know about you, but this site pinned my CPU while loading. The UI does not look complicated; a navigation tree and a view pane with text. I have never heard of Blazor before, but this is a very poor first impression.
- Semaphor 3y agoBlazor is a bit special in that as a full front-end framework, it’s (for now) more for heavy apps or internal ones, as it includes essentially the whole .NET framework in webassembly :D There’s an alternative called server-side Blazor, that uses websockets to provide interactivity. It’s a front-end framework that you can write in C# without touching Javascript, the current preview brings further performance improvements, but in general it’s not "eh whatever, let’s use blazor for our new site" the same way one might use Vue or React. All other components I’ve seen so far were pretty bad, one takes about a second for datagrid paging, another 100-300ms to open a drop-down.