Having lots of stuff in a doc page doesn't mean your docs are any good. I spent 2 years writing against the latest stable ExtJS. At about 3 months, I stopped u

Having lots of stuff in a doc page doesn't mean your docs are any good. I spent 2 years writing against the latest stable ExtJS. At about 3 months, I stopped using their docs for anything but cursory information: what methods does this class have of its own, what does it inherit, what is its class hierarchy, etc. That information is dynamically generated and typically spot on. The rest is generated by doc comments, and it's very hit or miss. Instead, if I needed to know ANY details of a function, I clicked on the '.js' link on the right side of the page in the class hierarchy to load the .js file in the browser, then a quick cmd+f would show me what I needed to know, because I can parse consistently formatted JS faster than I can grok their vertically challenged documentation. JSDuck pulls inherited docs if function-level docs are omitted in a subclass, too, and sometimes they're just plain wrong because of that. After about 6 months, I had committed to memory about 60% of Ext (all but the graphing bits, mainly, which I never used). I believe a good library is one that you don't need to worry about, ever. So naturally, being required to delve into Ext's source so often to me is unacceptable of something that is a paid product. I would've been fine to fix so much in Ext, but it isn't developed in public via something like github, even though it's dual licensed, which meant the only way to do that was to post on their forums. No thanks. 4.x came a long way in rendering performance, but there were still critical paths that were untouched, including layout logic that determined when to perform layouts. They aren't required almost ever, but are used liberally, so while making the process faster is a benefit, the fundamental problem remains. A 200ms (for us, YMMV) layout problem was fixed (down to < 1ms) by a +5-0 change that added heuristics to determine when a layout was actually needed. This is a trivial change, and could be thrown in a PR at no cost. I'm not going to copy my code on the forums and hope someone at Sencha will manually merge that into whatever bleeding-edge version they have.