In my opinion you need dojo-scaffold (now outdated) or dojo-boilerplate(still recommended by dojo developers) only if you do not understand dojo well. I am quit

In my opinion you need dojo-scaffold (now outdated) or dojo-boilerplate(still recommended by dojo developers) only if you do not understand dojo well. I am quite sure after reading the article I wrote you will not need any of those clutches, and do things the way you please. Dojo's learning curve is a big problem, and I am trying to do my bit to address that. The changes are confusing, yes, but what can you do? You can not live with old just to not make things confusing. I believe the great programmer bit is only another way of saying the documentations are lacking, and not that dojo itself is more "complex" than jquery (of course it does much more, so compare it with jquery+requirejs+backbone+<there is no widget library in jquery i believe>). Debugging is a pain in the ass, yes. I am not sure what is the answer to that. I am planning to do a few more articles, covering MVC etc in a little bit more detail. To me the first question is technology, dojo represents a solid, well thought out technology, secondary is documentation/learning. I would be willing to spend an extra week to learn something with sparse/confusing documentation, if it provides me with an edge when it comes to future work. And in my opinion dojo does.