On 12/4/06, Mislav Marohnić <[EMAIL PROTECTED]> wrote: > I don't approve the usage of the term "hacking" when using a natural feature > of the language.
I've called if prototype hacking for a while. I find it fits in with the general idea of doing something expedient that can possibly break. > This won't happen. There won't be new stuff added to JavaScript until > version 2, which will also include features like modules and > namespacing to allow code to run on its own island.... [snip] > But so far I've > encountered *only one* pragmatic danger of using Prototype, and it's a > by-product of the incorrect code of third parties. That's reasonable enough. When I initially made the decision in JavaScript, Object.prototype was in use which was much less okay. My current opposition is more theoretical, but I have, as mentioned, seen a monkeypatch in Python backfire and cause a lot of problems for people. When javascript grows namespaces in all the popular browsers^W^W^W^WIE, consider my objection dropped. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
