Prototype, DOJO, self made – what Ajax framework should we use?
So far I have always recommended to write a simple self-made routine for the [tag]Ajax[/tag]-driven sites if I think that the developers don’t have the time or skills to learn the [tag]prototype.js[/tag] [tag]framework[/tag]. If, on the other hand, the developers are skilled and there’s time scheduled to learn a complete framework I have recommended prototype.js. The recommendation is based both on the usefulness prototype provides, but also on the very beautiful way it’s coded. (despite that extending standard classes must not necessarily be a good idea).
Today Per Henrik Lausten made comment regarding my “Using Ajax to manipulate Lotus Notes documents” post. In his post I found out that [tag]IBM[/tag] is working close with the DOJO toolkit. This is very interesting and I will certainly try out [tag]DOJO[/tag] once again, it was some months ago last time.
I believe that a heavy, feature rich framework is only of use if all architects and developers knows what features there is and how to use them. I have seen many projects that are including several overlapping frameworks. In addition to this the developers have included there own tools.js, utils.js code with old, proved functions for opening windows, populating selection boxes etc. Such applications will be extremely hard to maintain in the future. Better to find one [tag]framework[/tag], learn it very well and stay with it.
UPDATE: Is Yahoo UI the way to go. It’s atleast what Interakt choosed and the post has some arguments aswell.
