Remove jQuery and browser DOM dependencies and support Server Side Rendering (SSR)

[ybarbaria]

I want to know if you have planned to transform your jquery component in angular2 component ?
Your response will determine the purchase or of your library.

[dxbykov]

Hi,
 
We don't have plans to convert our jQuery-based components into Angular 2 based components. As you know, JS frameworks are born and die and it doesn't seem to be a wise strategy to stick to a single framework, because one day we'll have to convert our components to some other kind. On the other hand, we understand that jQuery dependency in our components becomes a drawback, not an advantage. So, I would say that we have plans to remove this obsolete dependency. It will allow us to integrate with other frameworks more smoothly and natively produce fast components. At this point, I'd like to ask you what is the main drawback of having Angular 2 wrappers over jQuery components for you?

[ybarbaria]

Hi,

Thx for your response.

Because I don't want jquery make DOM manipulation, there is Angular way.
I want use component made in typescript and made with angular.
At the moment I'm testing Wijmo, IgniteUI and your library . Wijmo have made theirs components in angular2 and the performances are better.
For example wijmo's grid is faster than your grid, faster during loading, faster during sorting ...

That the reason I think angular2 component are more effective than jquery component inside angular2 app.

[jFensch]

Breaking the jQuery DOM dependency also supports running the Angular 2 outside of the browser (service workers, server rendering, etc.)

Direct DOM manipulation is inherently slow and we've seen better rendering techniques in React, Angular 2, and other modern tools.

[dxbykov]

@ybarbaria Your point is clear and we completely share it. I should say that performance is one of the top priority aspects for us. Removing jQuery from the core of our library will help us improve it.

@jFensch I wonder if server-side rendering is what you would definitely use right now if we had it or it's just what you want to have in the future. Or, better performance is the main reason for you as well.

[jFensch]

Allowing pre-rendering on the server is a major performance win. This is easily enabled now not just for Node.js servers, but ASP.NET Core too.

Steve Sanderson from Microsoft does a great job explaining:

https://vimeo.com/157273325

[dxbykov]

@jFensch I got you. In my question I just referenced another aspect of performance.

And thank you guys for sharing your thoughts with us.

[sidorov-alex]

Hi, do you have any plans to implement this? I think the server side rendering is very important due to performance benefits.