> Ya I agree that it can be hard to see effects occasionally. Nono. The point is that they should be codified and forbidden in places they shouldn't be used.

> Ya I agree that it can be hard to see effects occasionally. Nono. The point is that they should be codified and forbidden in places they shouldn't be used. I cannot describe how much this matters to anyone who hasn't "absorbed" the Haskell mindset. (That's not your fault, it's mine. "More research/explanation needed" on my part.) > ... and a much better alternative to using Java. Yes, but it only if you use it as a "better Java". It fails _hugely_ if you try to do anything "advanced"... as in actual FP like lenses and things. > I'd love to work on haskell or introduce haskell in places that i work but no way in hell would I ever succeed. This is also a cultural problem. Migrate towards microservices and... there you go! Nobody actually cares what it's implemented in. (I think this is a somewhat sneaky/underhanded way to introduce it, but it... works.) EDIT: If you want to see first-hand what I'm talking about try "monocle" or "shapeless", which -- while both being fantastically named and engineered -- fail on actual usage.