2 ms·
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 c
by 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 agoFair 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 :)