3 ms·

> If you are less concerned with pure functions and happy with largely imperative or hybrid imperative code, then yes it is difficult to find a compelling examp

> If you are less concerned with pure functions and happy with largely imperative or hybrid imperative code, then yes it is difficult to find a compelling example for Immutable. Meh, I don't see a lot of usage even with pure functions. JavaScript never really had any protections in it (minus the new-ish const and Object.freeze()) so most developers I know simply write as if something else has access to an object then it will mess with it so everything gets architected accordingly. Just seems to me a mostly non-issue in the JavaScript world. > so I think it's a case to call it "mature" rather than "abandoned". No I would most certainly call it abandoned. They have countless issues and pull requests from over half a year ago without even a single response from a human. While it may be a mature product, I would still call it abandoned.

WorldMaker 10y ago
Just because JS historically hasn't had too many protections built in doesn't mean that adding protections from a library aren't useful. Especially if you are coding from a functional language perspective (and not everyone believes this but JS can be a rather good functional language if you let it; it's not terribly far removed from the ML/OCaml family). For what it is worth, anecdotally, I've been doing a lot of heavy work with RxJS observable pipelines (in a CycleJS-based application) where Immutable has absolutely made a big difference in performance and stability of complex "four dimensional" (lots of changes over time) "shared nothing" (pure) state tracking. That may be a use of the language and a complex learning curve of a framework setup in which you never plan to work, but it's definitely an "issue" where libraries like Immutable and Mori turn out to be extremely useful (whether or not you think they are abandoned). I've heard similar anecdotes from people using various combinations of things like React and Redux with Immutable.
- BinaryIdiot 10y ago
  Fair enough. I wouldn't be surprised a lot of folks found good uses for Immutable.js. I just hadn't seen anything that would appear to benefit from it in my travels and I think having immutability is a bit oversold IMO :)

WorldMaker 10y ago

Just because JS historically hasn't had too many protections built in doesn't mean that adding protections from a library aren't useful. Especially if you are coding from a functional language perspective (and not everyone believes this but JS can be a rather good functional language if you let it; it's not terribly far removed from the ML/OCaml family). For what it is worth, anecdotally, I've been doing a lot of heavy work with RxJS observable pipelines (in a CycleJS-based application) where Immutable has absolutely made a big difference in performance and stability of complex "four dimensional" (lots of changes over time) "shared nothing" (pure) state tracking. That may be a use of the language and a complex learning curve of a framework setup in which you never plan to work, but it's definitely an "issue" where libraries like Immutable and Mori turn out to be extremely useful (whether or not you think they are abandoned). I've heard similar anecdotes from people using various combinations of things like React and Redux with Immutable.

BinaryIdiot 10y ago
Fair enough. I wouldn't be surprised a lot of folks found good uses for Immutable.js. I just hadn't seen anything that would appear to benefit from it in my travels and I think having immutability is a bit oversold IMO :)