TL;DR: I use Angular (or * framework) simply because I can rapidly develop the features and adhere to ALL the requirements. ExtJS doesn't suck, but it typically

TL;DR: I use Angular (or * framework) simply because I can rapidly develop the features and adhere to ALL the requirements. ExtJS doesn't suck, but it typically doesn't fit into scope or doesn't fit all the requirements. ExtJS is a great way to facilitate development when working with large data sets that involve (as you mentioned) CRUD utilities along with business validation constraints. With that being said, these kind of tools (And KendoUI too IMO) are being stuck inside intranet systems where the custom widgets and tools remain proprietary. No visibility == no hype. I work exclusively on FE stacks and if the choice is Angular or any other top TODOMC* frameworks, typically that means the requirements don't fit well with ExtJS. Most JS-engine driven apps typically require a responsive implementation (cross platform is a big business trend), ability to incorporate a comprehensive design, and being able to do it within a reasonable amount of time (which is associated with budget). ExtJS has a ton of overhead (especially browser performance and scalability in SPA sites), a large learning curve (IMO), and requires a ton of time to implement custom designs. This doesn't mean there aren't great tutorials or start kits, but its not something you can master within a week. Responsive support OOTB isn't there (KendoUI has solutions for this on their framework) and the only choice for reusable code for portable devices is an adaptive approach using Sencha Touch. This doesn't mean ExtJS is a bad choice, but typically ExtJS excels in desktop apps that are data driven with designs that were made for ExtJS (its rare to not recognize an Ext app if its built on Ext). There's my two cents. I'm sure Sencha is going to destroy me if they ever read this.