Slashdot Mirror


Five AJAX Frameworks Reviewed

prostoalex writes "Dr. Dobb's Journal reviews 5 AJAX frameworks: Dojo 0.3.1, Prototype and Scriptaculous 1.4, Direct Web Reporting 1.0, Yahoo! User Interface Library 0.11.1 and Google Web Toolkit 1.0. Each framework was tested in two basic scenarios — writing a 'hub' (titled collapsible link list frequently seen on sidebars of many Web sites) and a 'tab panel' (horizontal tabbed navigation bar). During the process, Dr. Dobb's Journal reviewers noted that 'Dojo provides more features and HTML widgets than YUI and Prototype' but eventually 'settled on the Yahoo! User Interface Library.'"

5 of 187 comments (clear)

  1. Security not a consideration? by Lux · · Score: 4, Interesting

    Curious. With javascript hijacking attacks just discovered a few weeks ago, security was not a consideration in the evaluation at all.

    I'm a bit disappointed.

  2. As a .NET developer by leather_helmet · · Score: 3, Interesting
    ASP.AJAX

    MS's toolkit has been great - FF & Safari support is a breeze in most instances, allowing us to develop our applications really quickly

    Having downloaded and hacking a few quick demos with the silverlight BETA API, I am looking forward to integrating the CLR in our future releases

  3. Use frameworks only when really need them by roman_mir · · Score: 2, Interesting

    You have to understand what you are using, as was discussed earlier often frameworks are not needed, simple custom script should be sufficient for most cases. However people do tend to wrap even simplest of things into large complex frameworks, supposedely for introducing commonalities, providing familiar interfaces, whatever. AJAX is just so simple that in most cases any of those would be overkill.

    As the article (I RTFAd) states there are many cons and pros using these various frameworks. The main cons were:
    1. Not supporting the development model chosen for the project.
    2. Not providing enough documentation with the framework.
    3. Not providing enough widgets (many widgets still have to be custom made even with the frameworks.)
    4. The framework is too large and impacts performance.
    5. The resulting code is difficult to maintain.

    The pros were:
    1. Not having to write the AJAX code by hand.
    2. Not having to write some widgets by hand.

    I would say there for those cases when it is absolutely decided to go with a framework, do mix and matching. Use the simplest AJAX framework and mix and match it with widget libraries, but not entire libraries, extract what is absolutely necessary, in all cases custom code will have to be created by hand.

  4. Comment removed by account_deleted · · Score: 4, Interesting

    Comment removed based on user account deletion

  5. Re:Frameworks by mongus · · Score: 2, Interesting

    Well, I tried to get it down to 10K but my compressor only got it down to 15K. Feel free to use it. For best results, feed the compressor the uncompressed version.