[kradroy]

I have experienced this as well. Perhaps coincidentally the type of language they're always obsessed with is a functional one. I've yet to see a dev who's rabid over mutable state. They're usually bonzo for free monads.

That being said, I've generally found people who are obsessed over a single "technological thing" at work (language type, language, framework, OOP dev principles) rarely produce anything of value. They're usually on a mission to prove themselves right at any cost. Flexibility and ingenuity are the keys to a productive dev career.

[darksaints]

"They're usually on a mission to prove themselves right at any cost." Exactly.

That being said I wish there were more devs obsessed with mutable state. Some problems are inherently mutable, and trying to make them immutable doesn't actually get rid of the state, it just pushes it around awkwardly. Classes, for as much hate as they get (mostly deserved IMO), are a godsend for those types of problems. And while they're helpful, stateful programming is still extremely hard. I really wish there was more innovation in this area.

[Tainnor]

You can work with mutable state in Haskell, you just have to be explicit about it (e.g. State monad).