So if I were asked to step off my sandy beach to board the good ship Dojo I wouldn’t mind a jot. When waving good bye to the tropical island paradise jQuery I’d be wondering how life will be sailing the seven seas with Dojo.
On tipping my toes in the water signs of trouble were quickly visible. Not so much with the Dojo base, which is great, but with it’s hairy siblings. Dijit and DojoX. To me these read a little unfortunately like ‘Da igit’ and ‘Botox”.
One the reason for looking at Dojo is that the company I work for, 42, is overhauling their production process by streamlining frameworks with Maven and the Atlassian Stack. I’ve got no idea what they were on about so I started to review the front-end side of things. It’s clear that some client-side widgets will be needed and in the case of Dojo these will involve Dijit & DojoX. These tools do great things and do them well but their doggedness of proprietary attributes in the static HTML just rub me the wrong way. So much so I considered to jump ship.
Dylan Schiemann does well to debunk some of the Dojo myths. However when he tries to tackle the whole ‘validation’ problem he comes out sounding like a fully qualified moron. He does, to be fair, point out that this mangling of HTML isn’t unique to Dojo so I started to realise that it’s not about who is the best but rather who is less likely to trash your house. From this point of view Dojo’s love afaire with proprietary attributes isn’t the worst punk rocker you could run in to.
I’m holding on to jQuery for now but Dojo Toolkit will have my blessing on some of the larger projects I’m involved with. Now, fingers crossed that ‘Da igit’ and ‘Botox’ can get their act together.