Weirdly, I have the complete opposite experience with dojo. The streamlined AMD loading makes it really easy to write modularized, structured projects and buil

Weirdly, I have the complete opposite experience with dojo. The streamlined AMD loading makes it really easy to write modularized, structured projects and build it into release bundles. The store concept and compliant widgets are excellent, and while admittedly much of the dojox stuff is fragile, the dijits in general are very well made. The charting and drawing modules, with fallbacks (SVG, canvas, VML, Silverlight) have also been great to work with in my experience. Can you give some examples of things you find unintuitive or confusing? What makes it more difficult to debug than other Javascript libraries? How do you find the documentation lacking? (The latter has become quite a bit better in recent years, you may want to look at it again if you haven't in a while). I can understand that dojo may seem daunting at first. After all, something as simple as $('#foo').html('<div>foo</div>').css(...).click(function(.... in jquery, takes a fair bit more effort in dojo. This, and I suspect, quite a few of the other grievances you have, stem from dojo's insistence on modularization. This seems unnecessary at first, but in my experience, pays off as your code base grows. My recommendation is to seriously consider it for any complex javascript application.