We used this thread to help us make the decision to tie ourselves to Kendo's MVVM feature awhile back. Recently, I've been reading a lot from Kendo about Angular 2 integration, like Telerik's recent blog post.
My question is if Kendo still recommends using the built-in MVVM feature, or if you are now recommending using a plugin like Angular 2. It just seems strange that Telerik is doing so much promotion with Angular 2, yet maintaining its own MVVM feature.
Do you all still recommend one over the other? Or are you only talking about Angular 2 so much because other developers are integrating Kendo into it so often?
1 Answer, 1 is accepted
0
Hello John,
The Kendo UI MVVM feature is here to stay and you can utilize it with our jQuery-based widgets if you don't want to depend on other frameworks which support the MVVM pattern.
In case you choose Angular for your app architecture, it provides MVVM capabilities which are even more advanced than the built-in Kendo UI MVVM feature, hence it is recommended to utilize Angular instead of our own implementation.
Note that for our Kendo UI Angular 2 components we won't rebuild our own MVVM but rather leave the developer to make use of what Angular 2 provides as core framework features.
Kind regards,
Sebastian
Telerik
The Kendo UI MVVM feature is here to stay and you can utilize it with our jQuery-based widgets if you don't want to depend on other frameworks which support the MVVM pattern.
In case you choose Angular for your app architecture, it provides MVVM capabilities which are even more advanced than the built-in Kendo UI MVVM feature, hence it is recommended to utilize Angular instead of our own implementation.
Note that for our Kendo UI Angular 2 components we won't rebuild our own MVVM but rather leave the developer to make use of what Angular 2 provides as core framework features.
Kind regards,
Sebastian
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!