On 7/19/06, Todd Ross <[EMAIL PROTECTED]> wrote:
but I still believe in Prototype-the-project.
I'm curious why. I've been reading different criticisms of Prototype.js on the web for months and wonder why it is the default JavaScript library for Rails. Perhaps there weren't many options avaliable when Prototype.js was chosen for Rails but that is changing. I would like to see Prototype.js out of Rails in favor of something more like the Yahoo! UI approach. More modular. More standard style JavaScript. Prototype.js tries to make JavaScript like Ruby. That is unnecessary as JavaScript is a fully capable language of it's own. Then Rails wraps Prototype.js code in Ruby. That is a lot of potentially buggy wrapping and not at all DRY! JavaScript is repeated by Prototype.js which is repeated by Ruby. Maintenance nightmare! All this along with the fact that the prototype.js project is not responsive is going to hold back the future success of Rails. Client-side code will be a bigger and bigger part of web apps as we head towards Web 3.0 (whatever that is) and beyond. For example, I virtually rewrote the scriptaculous drag and drop library to clean it up and fix about 15 tickets total. The whole thing deadended because I couldn't take the punishment that Prototype.js was giving to me daily. Peter _______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
