What I highly recommend if use dojo's declare way of doing object oriented javascript.
Specialized libraries are always going to beat general purpose libraries, but the reason big frameworks are popular is because they give a structure to the project. The dojo project I did will look quite similar and familiar to any other dojo developers, we will use same way to build our builds, same way to represent data using object stores, our classes will be compatible with each other, and our widgets will look familiar.
There is value in it.
Well if you're using the AMD syntax, that's what you're doing, albeit initially limited to the (extensive) dojo library.
I personally find the dojo core relatively simple to use. Each individual module is small enough to grok in a few minutes.
but in general, i'm beginning to despise monolithic "do everything" toolkits/frameworks like Rails, Meteor and Dojo - the level of "vendor lock-in" is hellish..
just stick to plain old HTML5, OO Javascript and simple, specialised libraries which can be mixed in as and where required.. make the libraries depend on your code, not the other way around.