I think spamming mutable objects around in your codebase is asking for trouble. I'd be really happy to be able to do something like this: foo( Object.copy(barObj) ); I mean, why would you send your state's mutable…
I think it is almost unbelievable that the ESxx train continues to expand the language with ever more features, while at the same time there is still no native method to deep-copy an object.. Almost everything in JS is…
It's an ad!
I think spamming mutable objects around in your codebase is asking for trouble. I'd be really happy to be able to do something like this: foo( Object.copy(barObj) ); I mean, why would you send your state's mutable…
I think it is almost unbelievable that the ESxx train continues to expand the language with ever more features, while at the same time there is still no native method to deep-copy an object.. Almost everything in JS is…
It's an ad!