Q: blazor components approach performance Recently working around to create blazor component, I have stuck with certain questions.


*

*What is the best approach to creating components( Native & Or Using Existing JavaScript UI)

*Is there any performance or memory leaks in choosing Existing JavaScript.

*Any impacts in Serve Side blazor While Using JavaScript Lib components.

*What are the pros and cons between both approaches?

A: *

*There is only a single approach in Blazor - creating Blazor UI components. Both Angular and Blazor are UI Component frameworks. The first employs JavaScript, the later employs C#, though you may use JSInterop when you can't otherwise.

*There might be some memory leaks when C# code is waiting for JavaScript response while JavaScript code "is not sure what to do". In that case, and as far as I remember, the Blazor framework is going to stop this nonsense after a certain time.  

*The objective of Blazor is to use JavaScript, as little as possible. Blazor is not a JavaScript framework. And it employs JavaScript in order to communicate with the DOM, at least until Web Assembly is mature enough to enable direct communication with the DOM, without the mediation of JavaScript .
Start learning Blazor... Blazor is awesome...
Hope this helps...   
