Why you have to take Dojo seriously…

The 28 days of Dojo has come to an end but the blogging will continue. I chose to do this little venture to learn and share what I have learned over the past few months with Dojo and to also evangelize Dojo to all of IBM and Lotus customers. As you have seen, I referenced a lot of material already on the net, and to be honest, that is where Dojo truly shines – the community. One might ask why I would this?

Well, I was never told to do this by IBM, nor was it part of some marketing campaign. I simply see the momentum and the determination by both IBM and its community to build the very best of breed JavaScript frameworks that can be deployed cross platform in enterprises all over the world. Any web based or even rich based applications at IBM are embracing and extending Dojo. As you will see in the next versions of Dojo, there will be amazing enhancements to this already excellent framework. There are teams, right now, working on some amazing widgets to be included in the next versions of their products. Learning and knowing Dojo will be vital to many products in the IBM portfolio, including Lotus Notes and Domino.

As with most of my posts, this post was written days or even weeks in advance. I will however, post the hit count results for this month when the 28 days of Dojo really ends. Hopefully by then it will show the level of interest. Of course, this is only one blog and there are so many amazing people evangelizing and promoting Dojo I could spend three months covering all of the blogs, articles, and books on the subject.

As I posted before, get involved! An open source project is only as good as the people who get involved with it.


3 thoughts on “Why you have to take Dojo seriously…

  1. We are currently using the dojo framework in a current project, panes, grids, trees, dialogs, sliders, etc., etc. We have been running into many browser client memory issues (IE memory grows and grows), stemming from grids, dijits (or our custom objects) that do not get destroyed if you are opening “documents” in tab panels, etc. We have identified that moving from 1.3.2 (default with 8.5.*) to 1.5 helps a lot, 1.6 also helps, but is just out of beta. Research indicates references to DOM and dijits (when referencing the same “object”) can get you into trouble. We are also noticing different behavior between ie6 (agh), ie7, ie8, ie9, Firefox, Chrome, Opera. dojo definitely speeds up client side dev, but is not without it’s pitfalls, I am sure many of these are coding errors, but we do also seem to be running into known bugs. I can provide further details when we have finished our audit, I’ll post to the 8.5 forum.

  2. @Nick, Ive noticed the same thing w/ browsers becoming memory hogs.

    With the latest and greatest Firefox, I’ve been using one of my xpages app and after 2-3 hours of the browser being open, FF is using up to 800mb of ram. Ridiculous if you ask me.

    I’ve now switched to Chrome for xpages use and the browser usually sticks to 50mb of ram, sometimes i see a 2nd/3rd chrome.exe in ram, but all still remain under 50-60mb

    My xpages app is basic xpages stuff (data tables and view display) and the extension library from openNTF

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.