When comparing Kendo UI vs Dojo Toolkit, the Slant community recommends Kendo UI for most people. In the question“What are the best Javascript UI Widget Toolkits?” Kendo UI is ranked 1st while Dojo Toolkit is ranked 3rd. The most important reason people chose Kendo UI is:
Kendo UI is separated into a commercial and open source frameworks. The core of Kendo UI is in the open source frameworks, but some usability and benefits of Kendo UI are lost without the commercial version.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Free Core tools
Kendo UI is separated into a commercial and open source frameworks. The core of Kendo UI is in the open source frameworks, but some usability and benefits of Kendo UI are lost without the commercial version.
Pro Platform-based UI
Kendo knows what device it is being viewed on so it can adjust the UI accordingly. If a user is on a PC the user will see things differently than on a mobile device. Between iOS and Android the user will also notice a different as it pulls from the core UI of those core systems.
Pro Theme Builder
An interactive tool that has been created to customize an apps theme. Users are able to select from many pre-defined themes, edit them, and download the theme to bring into a project.
Pro Highly modular
Dojo Toolkit is a highly modular framework. It uses AMD modules and the module system is extremely powerful and easy to learn.
Pro Consistent and complete
Pro Not only web apps
Dojo is not used only for web development. The widgets featured in Dojo can also be used to create mobile user interfaces.
Cons
Con Expensive commercial tools [$699, $1,499]
The other core tools developed with Kendo are the commercial tools. There is the Professional version for $699 that will result in more jQuery UI widgets and client support. The $1499 "DevCraft" Complete edition gets developers the DevCraft .NET toolbox, testing and debugging frameworks and applications, as well as priority support.
Con Not able to keep up with the future of the web
The web is moving towards web components, something that Dojo does not implement. In its current state Dojo badly needs more abstraction and it also needs to provide some form of modern application architecture.
Con Integrated first-party loader makes interoperability extremely difficult
Con No startup-function
When the dojo-javascript is loaded, it will directly run the application. No chance to intercept with the options