3 ms·

I could have done with this two months ago. I've just finished quite a large dojo project, and it has been a huge pain in the ass. It is impossible to debug, t

I could have done with this two months ago. I've just finished quite a large dojo project, and it has been a huge pain in the ass. It is impossible to debug, the AMD changes are confusing as all hell & it is badly documented, but its biggest flaw is that it has a hockey stick learning curve. You can get to jQuery mastery in your own time, but for you to produce anything decent with dojo requires you put a whole heap of unuseful headscratching in at the start. If you're a great programmer, then maybe dojo is for you. But if you're an average programmer who needs a degree of discoverability in the tools that they use, then I would steer clear. Another problem is that the framework is currently in a half-finished state (mvc anyone) and it looks like it's going to stay that way for a while. I think this : https://github.com/rmurphey/dojo-scaffold https://github.com/rmurphey/dojo-scaffold was posted a while ago, but if you haven't seen it - then it might be worth looking at. Again, I haven't used it, but if I had known about it before starting a dojo project, I would have given it more attention.

amitu 13y ago
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.

amitu 13y ago

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.