I've been using nRoute framework on silverlight, and some MVVM features that it provides, really is a miss on kendoo ui. 

for example some of the "killer features":
1. On a view, you can apply url like template attribute ("Content/Views/functionality/Loadstuff/{AccountId}") and the internal routing will find that and initiate, when it is called via global static navigate method.
2. The binding of View and ViewModel is done very well. On the view model, you apply attribute that this viewmodel is working with this view.
3. Containers. You can call navigate url, and get the rendered viewmodel. This helps application composition as you can have a some layout templates, and apply custom attribute on div, like "container-url" to some internal url, and it will fetch the rendered view and put it there.
4. Communication framework. Literally a Pub/Sub.
5. Modules/Dependency tracking. For example, i have SPA application, that loads some basic controls for js, and when user clicks reporting, it will check that reporting is dependent on Dataviz, loads dataviz, and loads viewmodel.
6. Behaviors, very common things, like, ValueNotNull, ValueNull, BooleanValue for someexpression. This allow you to create more dynamic ui, without adding new code in your viewmodel