News for hackers. Stuff that matters.
Re:Reflecting on Haskell in 2017 by AnimalMuppet on Monday December 04, 2017 @01:33PM (#15846251)
> That seems like a poor way to explain the concept since the entire point of programming is to mutate state and that's how the hardware actually works, too.

The hardware actually works using gotos, too (well, jumps in assembly language). That does not make it either ergonomic or safe to write code that way.

The entire point of programming is to compute results. In the hardware that results in mutations; in the programming model it doesn't necessarily have to.

Re:Reflecting on Haskell in 2017 by acdha on Monday December 04, 2017 @02:36PM (#15846739)
My point was simply that saying “immutability works when everything is immutable” often sounds confusing and/or wrong because people know they need to mutate things. Saying that you're using a language with more advanced concepts to ensure that things only change in the desired manner avoids that initial point of confusion.