3 ms·
Whenever monkey patching comes up, I always remember the time when a popular JS library forced an upcoming standard to change its name so as not to conflict wit
by brundolf 4y ago
Whenever monkey patching comes up, I always remember the time when a popular JS library forced an upcoming standard to change its name so as not to conflict with its monkey-patched addition: https://developer.chrome.com/blog/smooshgate/ https://developer.chrome.com/blog/smooshgate/
- masklinn 4y agoThat was an extension, usually the goal of monkey patching is to alter or replace the behaviour of an existing feature which is not exposed in a way which allows it (or you want to make sure nobody will use it wrong). So a monkey patch in the classic sense does not conflict with upstream updating their API. And because you’re in control and the upstream has no idea you’re doing what you’re doing, breakage will fall on you anyway v