News for hackers. Stuff that matters.
Re:The unintentional side-effects of a bad concurrency model by EvanPlaice on Thursday January 28, 2016 @02:59AM (#10986978)
Or, you know...

You could just use immutable.js.

It's not like OOP languages where the built-in data structures are built up from many layers of inheritance that all have to be made immutable. Where access is blocked at the language level (ex private/protected).

Immutabilit is not difficult in JS. It's just not immetiately intuitive unless you understand the value of comparison by reference.

The == vs === always seemed like a strange vestigial appendage of JS. With the recent trends, it's beginning to make a lot more sense.

There are no comments on this comment yet.