Telerik KendoUI vs Sencha ExtJS? [closed]

Question

We are going to build a enterprise grade application on Web and for that we have filtered down our choices to ExtJS and KendoUI.

Both are decent and have rich features / controls, KendoUI is faster in performance than ExtJS but then ExtJS is like much more complete package which includes every component required to build desktop like web application and Grid seems more powerful.

on other hand with KendoUI we have power of jQuery and feel like home familiarity and almost zero learning curve because team already uses jQuery.

Does anyone have experience building large enterprise class application using either of them? and if yes what is your experience? Please share be it bad or good so that I can have some ground before I end up going with anyone of them for long time.

I am leaned towards ExtJS more because we are going to use a scheduler control which is from CubeDrive (myCalendar) which is again in ExtJS.

So your thoughts and experiences are welcome for helping me taking a right decision.

Answer 1

This is not a question that can be answered by us. You already give a solid overview for your team (which is all that matters):

Same

• rich controls

ExtJS Pros

• more widget components
• scheduler control

ExtJS cons

• Sencha does not make its source code available on GitHub for pull requests
• There is no public issue tracker

KendoUI Pros

• faster (I'm not so sure about that)
• no learning curve
• jQuery community support
• Material Design theme

KendoUI Cons

• smaller set of widgets in the open source Kendo UI Core (grid, charts are in the Professional version)
• no Architect

I'm sure an application can be built with both frameworks. What's more important to you? Fast delivery (you say that your developers can jump right in with KendoUI), or strategic orientation for the future?

That being said, we are developing with ExtJS. We are generally satisfied, with some caveats:

• The documentation is often outdated or incomplete (that's improving with recently introduced community comments)
• It not trivial to expand the functionality of some built-in widgets