4 ms·
It's the kind of thing that could possibly be OK in nodejs but is not OK in the browser. My biggest problem with it (and how it goes down in Rails for that matt
by rgbrgb 13y ago
It's the kind of thing that could possibly be OK in nodejs but is not OK in the browser. My biggest problem with it (and how it goes down in Rails for that matter) is that you can inadvertently clobber variables in namespaces you don't own. Changing the prototype of String there will change it in the context of every 3rd party library that's also running. It just doesn't scale with the codebase.
- secoif 13y ago> possibly be OK in nodejs but is not OK in the browser. I think you've got that around the wrong way. It's more of a problem in node/browserify because you're typically working with very many more 3rd party libraries.
- rgbrgb 13y agoYeah, that's fair. The bottom line is please never do it or teach noobs to do it without telling them why it's wrong.