Re:What every systems programmer should know about concurren...
by adrianN on Friday December 13, 2024 @10:44AM
(#42409554)
Of course you can have only immutable data, you just need suitable monads.
[ Parent
| on HN ]
Re:What every systems programmer should know about concurren...
by hyperpape on Friday December 13, 2024 @12:04PM
(#42410273)
There's disagreement about what exactly makes you a systems programmer, but dealing with the reality that memory is finite is definitely a requirement.
You need mutation or garbage collection (and systems programming is the kind of environment where that's not just "someone else's problem").
Re:What every systems programmer should know about concurren...
by kccqzy on Friday December 13, 2024 @12:34PM
(#42410534)
Plenty of languages have immutable data without monads or even being statically typed. Clojure is a fine example. And there is also the somewhat popular https://immutable-js.com/ that brings the benefits of immutable data to JavaScript.
Re:What every systems programmer should know about concurren...
by SideQuark on Saturday December 14, 2024 @10:07AM
(#42417556)
By that argument, all programming is immutable, with monads only used to update the mutable parts.
The point of this article is to detail needs for those monads to interact in a concurrent manner.