| While I'd agree that the documentation could really use an overhaul, once you figure out what the "modern" way to use it is - I've found it to be none of the things which you describe it. I recently implemented an application on the 1.6 version of Dojo, and found it pretty easy to set things up using an MVC pattern which, while I could have implemented myself in JQuery, would have taken longer and wouldn't have been built to the standard Dojo expects. Here are a few things I like about it: * It has a layout manager, so I can build fluid UIs that are divided up into various content panes that react via the MVC model. I tried a few different layout manager options out there under JQuery, and none of them integrated well with other libs I wanted to use. * It has an event bus built in, which means I can decouple components but allow them to communicate asynchronously. * It has a wide range of components that I can drop in, rather than writing myself. * It's component model is actually kind of slick. You can define a view file, which is just some specially marked up HTML, and then a backing code file for it, which acts as the controller / event manager for the file. You can then define classes at the page level that act as controllers to wire up all of your individual components. No generation via strings. * It has a built in dependency mechanism that dynamically loads only the components you need for a given page. It also has a build system that lets you package up only the components your application actually uses. Sure, I could hunt around and try and duct-tape each of these pieces together individually with JQuery, but for my use cases, the "batteries included" model worked really, really well. |