Just let it go man. I'm guessing that the vast majority of people on this list have heard all the arguments against prototype before. It is just one of those libraries that you either love or you love to hate. Your not helping anyone anyone at this point. I love the 'sugar-on-the-top for Ruby devs' and I purposely decided I would accept any performance hits, as minor as they may be, to have a more efficient and frankly more fun way to write my _javascript_. It isn't for everyone and it doesn't try to be. You can find that with other heavier libraries.

Several of your arguments are a little puzzling to me though. You mentioned that this library uses userAgent for browser testing. You do know that this isn't the only library that does that and on occasion it just isn't practical to feature test.

You also mentioned the size. In my experience this library is small and is a great starting point for extending. Especially when compared with Dojo and YUI. Those libraries felt a little to heavy for me and way too painful to continuously have to be typing out namespaces. Before I get flamed for that comment, I completely understand the need for namespaces on libraries that try to be all to all and work with other libraries. For me, this is not necessary. I just need a good foundation and I'll add what I need and what I don't need. I'm not going to mix other libraries whole sale.

Now I have my gripes about prototype just as much as anyone else but I'll add my patches and if they are good enough they will be applied, eventually.

Bottom line ... prototype takes away a lot of the pain and has been a great foundation, for me.

Enjoy your namespaces.

On 7/20/06, Peter Michaux <[EMAIL PROTECTED]> wrote:
Hi Thomas,

On 7/20/06, Thomas Fuchs <[EMAIL PROTECTED]> wrote:
> "I think Prototype.js is a lost cause by design."
> So-- then what are you doing on the Prototype/script.aculo.us mailing
> list? :)

This is the Rails spinoffs list. It is the choice of Prototype.js as
the default _javascript_ library in Rails that I am contesting.


> The sole point of Prototype is to give the programmer a powerful,
> opinionated
> toolset, to make programming _javascript_ less pain

That is a great idea but unfortuntely, prototype.js ends up making it
more pain because of the many concrete reasons I listed before.


> (with some extra special sugar-on-the-top for Ruby devs).

But they are _javascript_ devs when they are programming _javascript_.


Peter
_______________________________________________
Rails-spinoffs mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs

_______________________________________________
Rails-spinoffs mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs

Reply via email to