What is the benefit of moving to Kendo from say asp.net ajax (non-mvc). It seems the Ajax controls now have HTML5 charting elements and the other existing ajax controls provide "touch enabled" capabilities for mobile devices with the .js resource files. So what then is the benefit other than SOE and lighter weight controls as two big reasons (neither of which a big concern to my product)?
Any glaring and big reasons one would make the switch?
The only anwser I've found was from this thread and not sure if that's pretty much it and it truly stands still:
http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/asp-net-ajax-versus-kendoui-clarification.aspx
"This basically should be an architecture decision based on the target users of your application and the goals of it. If the idea for everything working on the client fits your needs, you can try Kendo. If you still prefer the server-side approach, you should continue with ASP.NET AJAX components. "
Any glaring and big reasons one would make the switch?
The only anwser I've found was from this thread and not sure if that's pretty much it and it truly stands still:
http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/asp-net-ajax-versus-kendoui-clarification.aspx
"This basically should be an architecture decision based on the target users of your application and the goals of it. If the idea for everything working on the client fits your needs, you can try Kendo. If you still prefer the server-side approach, you should continue with ASP.NET AJAX components. "