Comments on: Javascript barriers to rapid development http://blog.wioota.com/2007/01/24/javascript-barriers-to-rapid-development/ I have nothing to say and I say it. Thu, 04 Dec 2008 18:54:16 +0000 http://wordpress.org/?v=2.6.3 By: wioota http://blog.wioota.com/2007/01/24/javascript-barriers-to-rapid-development/#comment-1200 wioota Sat, 27 Jan 2007 04:34:08 +0000 http://blog.wioota.com/2007/01/24/javascript-barriers-to-rapid-development/#comment-1200 Script.aculo.us was better than prototype for documentation and I definitely think their approach to drag and drop was easier to get into than YUI. Both libraries suffered from over-simplified examples which I feel may have also been used as the use-cases for implementing the libraries. Our use of YUI for a customisable page ala Google Personalised/MSN Live etc. unearthed issues in their Intersect mode implementation, overlapping target areas and other complexities bound to found in applications which go beyond a simple list or set of drag zones. In these situations the documentation didn't help but an extra dimension that both libraries do bring to the table is their respective communities which do help close the loop. Script.aculo.us was better than prototype for documentation and I definitely think their approach to drag and drop was easier to get into than YUI. Both libraries suffered from over-simplified examples which I feel may have also been used as the use-cases for implementing the libraries. Our use of YUI for a customisable page ala Google Personalised/MSN Live etc. unearthed issues in their Intersect mode implementation, overlapping target areas and other complexities bound to found in applications which go beyond a simple list or set of drag zones. In these situations the documentation didn’t help but an extra dimension that both libraries do bring to the table is their respective communities which do help close the loop.

]]> By: Ben http://blog.wioota.com/2007/01/24/javascript-barriers-to-rapid-development/#comment-1190 Ben Thu, 25 Jan 2007 11:07:31 +0000 http://blog.wioota.com/2007/01/24/javascript-barriers-to-rapid-development/#comment-1190 I am in complete agreement, based on my own experiences (which are actually with Prototype, not YUI, but I'm sure the same reasons stand). I found the complete absence of documentation baffling at first, as the popularity of the library seemed to suggest there was something great about it. There was more documentation (although I should point out it is still not great) for script.aculo.us, which depends on Prototype, than on the prerequisite library itself. Final pedant point though; you mean <a href="http://www.wsu.edu/~brians/errors/allude1.html" rel="nofollow">allude</a>, not elude. I am in complete agreement, based on my own experiences (which are actually with Prototype, not YUI, but I’m sure the same reasons stand). I found the complete absence of documentation baffling at first, as the popularity of the library seemed to suggest there was something great about it. There was more documentation (although I should point out it is still not great) for script.aculo.us, which depends on Prototype, than on the prerequisite library itself.

Final pedant point though; you mean allude, not elude.

]]>