Tony Morris

That's why I rather write my code in Haskell instead of having half assed effect tracking in Scala

There is a good reason to not write IO in Scala. This reason is not one of them. It's not good reasoning.

What would be the good reason to not write IO in Scala then, except the obvious performance hit ?

The same reasoning writing anything in Scala is a bad idea. IO takes more than a performance hit. It's untenable.

I acknowledged the reasoning part. But it seems you agree with me on the big picture unless I misunderstand you

"Don't write IO in Scala. Don't write anything in Scala." IO in Scala is just as safe as it is in Haskell. Reasoning otherwise is busted.

In theory you're right. But making your way out of IO in Haskell is very painful and unpredictable. Good luck writing a complex program

While doing the same thing in Scala is... well writing Scala as it was designed, without an effect tracking system