Is this correct for Javascript?
https://github.com/tc39/proposal-change-array-by-copy
This is my opinion about it: This kind of proposal are very harmful for JS/TS.
What will we do? Duplicate every method that could create a new modified Array/Object?
The learning curve got duplicated for mutable methods. Why do we allow this? We need to stop this at its roots now that we have time, before it's too late.
I don't know where could i do propose this, but i have to express myself:
I want to remove those stup*d new methods an create a new one called
This is my opinion about it: This kind of proposal are very harmful for JS/TS.
What will we do? Duplicate every method that could create a new modified Array/Object?
The learning curve got duplicated for mutable methods. Why do we allow this? We need to stop this at its roots now that we have time, before it's too late.
I don't know where could i do propose this, but i have to express myself:
I want to remove those stup*d new methods an create a new one called
.clone().clone() that allows to developers clone the object...GitHub
Provides additional methods on Array.prototype and TypedArray.prototype to enable changes on the array by returning a new copy of it with the change. - tc39/proposal-change-array-by-copy
