I remember in one of the Sencha presentations talking about a framework where you could actually record what you were doing in the sense of snapshots, then if a snapshot changes for sure the application was broken. This tool was suppose to be released by Sencha, but never saw the light of day.

Then I think they should use the docs to let the people know about Siesta. Let me rephrase my statement: they should promote in the guides the use of some sort of testing framework (Siesta) in the same way that Angular does.

ExtJS and AngularJS are to different frameworks and both of them have their strong points. Ext have widgets which is their strongest point againts Angular, and other great things; but Angular have data-binding, route support, a better MVC design and is by faaarrr more testable than Ext. Also is MIT licenced and the development is open on Github.

It's not a joke and the car vs tire comparison was fair. Just compare the number of code lines in AngularJS vs Ext JS.

AngularJS feels more like a programming language (HMTL6) and Ext JS is a full-blown framework with a strong data package and a rich set of components.

AngularJS feels more like a programming language (HMTL6) and Ext JS is a full-blown framework with a strong data package and a rich set of components.

That's the point. They have different aproaches to solving differente problems. It's true than ExtJS codebase is by far biggest, but that's is not really important in this context.
My point is that you can't use Ext for every kind of site. It just overkill and sometimes odd. Take for example a single page shop application. For something like that I prefer Angular with it's HTML6 aproach. You can also do it with Ext but, is it worth? How about the Ext styles? I prefer to style my shop with something like Bootstrap instead.

Discussions should be started between Ext and Dojo (out of the question which one is better...) and between Angular and EmberJS.

It's also easier for the Angular team. First, they got to start with a blank slate, while Sencha is continuously migrating an existing codebase. Second, Angular has no class system or any of that sort of feature set. And finally, they're not dealing with the complexities of a gigantic UI component library (covering old IE to latest browsers, and mobile to desktop).

As aesthetically pleasing as Angular is (there's no doubt they've done a good job so far), they seem to be focusing on the wrong things (at least to me). My main challenges in building large-scale MVC JS RIAs aren't in the M or the C, they're in the V. I use Deft JS on top of Ext, so already having ViewControllers and IoC and Promises, etc. means my client-side control, service, model, and data layers are pretty easy to deal with. Where Ext still destroys the competition is at the view layer. If Angular had a comparable component library, this discussion would be different. But they don't seem to be doing much in that area yet.

I agree that Ext isn't the right fit for every site. But I build complex RIAs (I came from a Flex background), and what's out there right now for Angular is just woefully insufficient for what I need.