3 ms·
We've already learned from our past mistakes changing the prototype of the standard library - the Ruby community learned the same thing with monkey patching the
by jamiepenney 9y ago
We've already learned from our past mistakes changing the prototype of the standard library - the Ruby community learned the same thing with monkey patching their standard lib too. The maintenance overhead far outweighs any immediate benefits.
- megous 9y agoWhat maintenance overhead? Current and future costs are reduced by making code simpler and cleaner in the first place by using prototypes efficiently. Also, to be clear, I'm suggesting adding new methods to DOM object prototypes, not changing behavior of existing methods.
- ehsanu1 9y agoApplications may be able to do this in a controlled manner. Library authors never should.