21 Oct 2013 3:31 AM #1
Kendo UI Vs Sencha js ?
I am currently researching on selecting a better UI framework for an highly scalable application. After doing lot of googling and reading lot of blogs, i have narrowed my options to Sencha JS and Kendo UI frameworks.
I am looking at below aspects. Can someone compare both frameworks and help me select right one.
- Time taken to learn and ease to use ? Some blogs are suggesting kendo ui learning curve is fast as it is developed on Jquery compared to Sencha Js. Learning Sencha is difficult ?
- Which one is easy to debug and enhance ?
- Which one has more HTML5 support ?
- Performance on mobile devices ?
- External support like documentation and wikis?
- Which one has more enhancements & development in pipeline ?
- Which is preferred for highly scalable cloud based applications ?
- Availability of source code for modifying for internal product development ?
- Kendo is providing theme builder. Is this feature so special which is not available in Sencha ?
- which one is light weight framework
- Ease of testability and support of existing test frameworks
- People are suggesting kendo UI beats sencha in browser speed. Is it true ? What are the ways to improve performance?
- I have come across some statements like minified version of js file is also very large to use. It is not good to use multi page applications. This is mainly intended for single page applications. It is correct ?
- What are the main important areas where Sancha Js beats Kendo UI ?
- Does sencha js provides more complex widgets than kendo UI ?
21 Oct 2013 9:47 AM #2
I don't know internals of Kendo UI, but by looking on their site seems that is one framework for both Desktop and Mobile, which is not the same for Sencha - at the moment has 2 different products, one for each platform.
So you could specify more clearly what you mean by saying Sencha JS, is Sencha Touch ? so that the community could help you.
21 Oct 2013 5:58 PM #3
Thank you for taking time to look at this post. I am actually exploring options for mobile and desktop. My application is same for both mobile and desktop. How much code changes are required if we have to use same one in both mobile and Desktop.
What is the learning scope of Sencha JS. Can you please share your experience of working with Sencha and also give main areas where you are not much convinced with Sencha JS. It will help me to get full picture.
22 Oct 2013 12:55 PM #4
Irrespective of which solution you choose, be sure to take an object-oriented approach to building the system.
Last edited by kmiklas; 24 Oct 2013 at 9:46 AM. Reason: Rewording
29 Dec 2013 3:59 AM #5
Due to the bugs reported in Sencha i decided to have a look at Kendo,but honestely I didnt understand the concept of Kendo,I dont know why somebody in the world releases a new product without OOP in mind.
Of course I dont like this strategy of SEncha to live with Bugs until the nest version,the same thing just killed Borland.
The fact that Express(Node.Js for human beings) are maintened by people who works for Sencha score some points to ExtJs too.
EXTJS 5 is taking a live to be realeased ,maybe it wont introduce new bugs.
ABout ExtJS being slow,I really think to be a sily thing to benchmark them on IE7.
At least for the kind of system I build(ERP/CRM),Kendo does not have things like Architect,and Sencha Space.
And of course the most important thing OOP.
Also I have allways made my life with DElphi, that was a really buggy software,there is allways two ways to do the same thing,and at least with EXTJS Im going to have the sources something I didnt have with DElphi.
29 Dec 2013 1:02 PM #6
Of course, it would be much easier to keep track of issue status if there was a proper Jira or YouTrack system in place. But that's a topic that has been discussed extensively elsewhere in the forums.
29 Dec 2013 2:52 PM #7
29 Dec 2013 3:07 PM #8
Another thing ,I´ve read many starters saying that the EXTJS learning curve is much bigger than Kendo ,Angular and so on.
But in my opinion these people probably are not used with OOP,So OOP might be the biggest part of this learning curve,but every seasoned OOP programmer knows that you become much more productive after mastering it.
30 Dec 2013 1:42 PM #9
Honestly, the biggest part of the learning curve is the sheer size of the API. You basically need to get used to having the docs open in a browser tab ALL THE TIME, for reference.
This is one reason I really, really wish Sencha would get behind TypeScript, since it eliminates these issues on top of doing compile-time error checking (which eliminates a huge set of potential errors). They wouldn't have to write the frameworks in TypeScript, just produce valid definition files. I've generated definition files myself for Ext JS and Touch by parsing the JSDuck output, but that's got a lot of problems (not the least of which being that the docs are just incorrect in many places).
30 Dec 2013 4:03 PM #10