It's a very specific project. I will never have any control about the JS being injected in the application.
So, I either loose my hair and go with Vanilla JS (I really don't want to go that way), or figure out a way to get Moo not extend natives. O. On Nov 13, 2011, at 9:04 PM, Sanford Whiteman wrote: >> Yes, I know this is the power of MooTools, at least it was, these >> days extending natives is just a pain in the neck > > Oskar, is it a pain in the neck because there's another framework > doing the same thing in this project? Browsers have ever-growing > support for extending natives, so in your experience, is it getting > real-world worse by being more popular and leading to more collisions? > Or theoretically worse because the wider availability is in turn > provoking more "political" objections (which I don't buy)? > > YMMV, and I know about the movmement afoot to the contrary, but as > long as you control all the JS, I think things are getting better out > there for extending natives. At the same time, though, any opaque, > third-party "utility" scripts (like analytics, live chat, ads, all > that stuff) must avoid extending natives. And since that cannot be > enforced, I can see why one might want to wrap everything. Sucks. > > -- Sandy > >
