When comparing Kendo UI vs Blocks.js, the Slant community recommends Blocks.js for most people. In the question“What are the best JavaScript libraries for building a UI?” Blocks.js is ranked 10th while Kendo UI is ranked 14th. The most important reason people chose Blocks.js is:
Blocks.js is just 16.5KB minified and gzipped. So it's pretty small.
Specs
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 Small footprint
Blocks.js is just 16.5KB minified and gzipped. So it's pretty small.
Pro Modular structure
Apps developed with blocks.js are modular in structure and make use of reusable objects. This makes these applications very maintainable.
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 Relatively new
Blocks.js is a relatively new library. It doesn't have much support and there re not many people who use it. So if you run into any problems it would be hard to get solutions.