Are there problems with adding new methods to built-in object prototypes in patching?

Adding new methods to the prototypes of built-in objects (for example, Array.prototype or String.prototype in JavaScript) can lead to several issues:

• Name conflicts: If the language standard adds a method with the same name in the future, it can cause unexpected errors.
• Enumeration problems: Methods added to the prototype may appear in for...in loops, which disrupts the enumeration logic.
• Compatibility: Other libraries or code may not expect changes to prototypes, leading to bugs.
• Support and debugging: It becomes harder to understand where new methods come from, especially for other developers.

Therefore, patching built-in object prototypes is considered bad practice and should be avoided, favoring composition or extension through separate functions and classes.