As a result the good experiences I had with their components in a SL context I am know adopting their KendoUI components together with ReactJs. So far all the points made above for SL still stands for KendoUI.
So to answer your question, from my experience using KendoUI reduces the time needed for the average developer to complete the task.
I have personally fought to work around their widgets more times than I've worked with them. And have dropped integrating their widgets into new projects, to avoid the bloat/overhead.
I've used a fair few .NET controls from various vendors and they all are challenging in different ways. The common problem is that they force you to do things in a particular way.
If I was to rebuild our product it would not be using any of this heavy backend style server controls.
It is history as far as I can see. JavaScript front-end frameworks and REST services even with .NET is where Microsoft seem to be headed as well.
In final stage, client asked for empty values support, i check and found that in next release they have this feature. So i said yes and gave them 1 week estimate. Assuming all i have to do is replace radchart dll.
But, I was wrong. I upgraded the Radchart and found 70% code is not working. Forget working, it's not even compiling anymore. Insted of deprecating the method, they remove it right away in next minor release.
I don't think there was any architect or senior programmers in their team.
In my previous company designers or managers fell for their shiny features and got trapped. Crappy product!
Another HP+Autonomy kinda scam.
I, like many people here by the looks, spent a good deal of time removing them. We had one issue where the page response with an AJAX Manager (or whatever it was called) was 5x as slow than a full page refresh. Turns out it was POSTing 2Mb of crap for some reason.
I'd rather eat my own poop that use their software again.