Thanks for your the valuable insight. I went and evaluated a few as well based on your video. I like many of them but they all have something missing. In the end, I ditched Radzen for MudBlazor as it was the closest to my needs. My views are: Radzen: best set of (60+) components, but not able to choose themes unless you pay. CSS is hidden within the nuget package and cannot be changed unless you recompile (yuk!). That was the game changer for me. Imaging writing an Web app without being able to use CSS, which has been around since 1998. MatBlazor: no chart support at this stage nor Googlemaps. I suppose I could get by writing my own or using something else. Great theme support but don't know about CSS support. Synfusion: don't want to be tied to a corporate for stuff where you can get opensource or free. Mind you I will support whoever writes good stuff that I use, but I don't want to be tied down. MudBlazor: Tables not as visually nice or functional as Radzen nor MatBlazor, but they will suffice. Don't have Googlemaps support unlike Radzen. BUT they support themes and (supposedly) you can use CSS. Also fast load times because written in C# instead of layers of wrapping around JS.
Been working with Radzen for the last 6 months, tried rewriting on mudblazor. Somehow it felt easy, smooth and enjoyable. If you don't have heavy data-grid based system, mudblazor is the one to go.
@@lardosian Hello, I use a use an injected service to maintain app state. A pattern I learned from watch Carl Franklin Blazor train on dev express channel. There are other ways to manage state, but this approach was so clean.
I have coded with Syncfusion and Radzen, I had a deep feeling that Syncfusion is very slow, in fact, that's why I googled and came to your video, thank you for your investigation - appreciated.
Radzen is deceptive. They advertise as being open source and free -- but it's only FREE FOR ONE APPLICATION! That's deceptive. I plan to make more than one Blazor application so won't use Radzen.
I am playing with MudBlazor now and was using Radzen. I still like RadZen better, but MudBlazor has a lot of upside if they can make their documentation better. I never bothered with SyncFusion because of their payload so I cannot speak to their controls. Overall, I like MudBlazor and I hope they expand more.
Coming from React and Material UI mudblazor looks very familiar. How is front end state managed in blazor, I really like hooks so hopefully it's similar.
Syncfusion blazor components internally are apparently using their js controls wrapped in the js interlop.. which makes sense looking at their size and lack of speed, mudblazor goes out of its way to try and be as close to c# as possible, hence the speed and size
False, it was like that for their first v1 version, which is very old. Make sure you're not using the wrong version. The second version forth, they rewrote everything natively in C#.
also we have to mention that mudblazor only use js when it is nessary otherwise they go with pure C# and it kind of easy with there wireframe and pre configured templates
I agree perfectly with you on Syncfusion's long loading time. I had to change almost all my Syncfusion components to Radzen because of latency issues, especially the SfGrid. Good evaluation there!!!
You're using it wrong. Just ask yourself, why do their demos, which have tens of thousands of rows (check that demo where you can select the dataset size), don't have these issues? You think they'd be in business if it was like that? And ask for $2000/developer/year?
