Reputation: 30292
I'm now getting into Blazor and wanted to understand if there's any benefits to using certain Blazor components such as DatePicker
or Chart
from third party vendors versus using some JS based solutions?
I know that the JavaScript Interop allows Blazor apps to use JS solutions so both Blazor component and JS options would be available to me but wanted to understand if there's any advantage in using Blazor components.
P.S. I have a little hesitance to use third party Blazor components. One small observation so far is that the DatePicker
component by Radzen actually did not open the date picker on my iPhone. This doesn't help overcome my hesitance to use Blazor components vs the JS option.
Here's the link to this component:
https://blazor.radzen.com/datepicker
Upvotes: 1
Views: 2141
Reputation: 119
I'd prefer to use stable Blazor components rather than trying to adapt current JS components into Blazor, because it'd take a lot more time and it's error prone
I've used Radzen and MudBlazor, and I think Radzen has more components available but MudBlazor looks prettier. MudBlazor has a preview (beta) datagrid and there would be breaking changes on further releases while Radzen datagrid is in stable version. Both datagrids offer server side pagging.
In any case, both suites could speed up the development time, but you'd have to invest some time to learn how to use them. Just pick one and start learning.
I've added both suites in a Blazor wasm project and they seem to work fine together, I used MudBlazor as first choice and I pick up missing/stable components from Radzen like datagrid or file uploader. The drawback of using both suites is a bigger download size, but I trust in the browser cache.
Upvotes: 1
Reputation: 4216
For me, using 3rd-party components of any flavor is a waste of time. Why try to get Radzen (or anything else) working the way I want, when Blazor makes it so easy just to create my own components? Trying to "save time" by fitting other people's work into my own projects robs me of my agency over the project, and generally leads to hours (or days) asking "How to I get ABC to do XYZ"?
The only component I know for sure I'd need 3rd-party would be an HTML editor. I just don't have the time for that.
ALSO-- a big part of custom libraries was difficulty doing anything cool in HTML in the past. But current HTML, current browsers, and the current state of Blazor, so much "just works" out of the box.
Upvotes: 1
Reputation: 1626
The only advantage you get is - it saves your man hours other wise you need to invest to build exactly what the third party components do. Other than that there is no other perceived benefits. If you have all the time in the world to sit and code a component, take care of all scenarios that the component needs to support, bug fix etc. - by all means you can do that. Radzen is one of the popular free open source blazor component library. Having said that you will need to first make a thorough evaluation of the library for your situation and then decide whether you want to use it or not. If you find a bug - go raise a issue on its Github repo and help them out.
Upvotes: 2