This topic has been completely exhaustingly beaten to death by every
single JavaScript conversation ever. The general consensus is that until
customizable iterators in JavaScript 2.0 become widespread, avoid
Object.prototype like the plague. All the other alternatives are too
heavy to be worth it, especially in the time-sensitive world of
JavaScript. I believe is that we, as a community, cannot and should not
be expected to handle broken code. And until the language can handle
Object.prototype intelligently, any use of it is broken.
-blair
Arrix wrote:
> I'm writing a bookmarklet application using jQuery and it fails with
> any page that uses Prototype 1.3.1.
> I found that it's Object.prototype.extend that breaks jQuery.
> jQuery's extend method gets overwritten after the first call to
> jQuery.extend({/**/}).
> It's rare to use jQuery and Prototype 1.3.1 together, but it's
> absolutely possible that jQuery will coexist with some poorly written
> code.
>
> Anyway to make jQuery more robust?
> Can we check hasOwnProperty() before copying properties inside
> jQuery.extend?
> Or can we have a black-list to filter out properties that conflict
> with jQuery?
>
> --
> Arrix
_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
