Thanks for the awesome comment. I really enjoyed it as a whole but I will highlight a few parts for further discussion if you don't mind.
"to keep our state in consistent state"
This is a bit vague for me. How is mutable state inconsistent?
"All race/deadlock conditions, concurrent update problems go away"
This is true for multi-threaded languages but I don't think this is an issue in case of (the mostly single-threaded) JavaScript.
"also provide other benefits such as memoization, time travel, etc"
I totally agree with this one, immutable updates really shine here.
PS: Thanks for the link to the book.
Thanks for the feedback, Miklos.
What I meant was variables don't change thus wherever you access that variable, it's always the same (consistent). Maybe it came out wrong 😅
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the awesome comment. I really enjoyed it as a whole but I will highlight a few parts for further discussion if you don't mind.
This is a bit vague for me. How is mutable state inconsistent?
This is true for multi-threaded languages but I don't think this is an issue in case of (the mostly single-threaded) JavaScript.
I totally agree with this one, immutable updates really shine here.
PS: Thanks for the link to the book.
Thanks for the feedback, Miklos.
What I meant was variables don't change thus wherever you access that variable, it's always the same (consistent).
Maybe it came out wrong 😅