You can use types to help with the outside world by making error states explicit encoding them in types. ZIO for example. I can write programs without code cov

You can use types to help with the outside world by making error states explicit encoding them in types. ZIO for example. I can write programs without code covering all scenarios by stubbing out methods with types, using ADTs etc then it’s a case of implementing a function to run it all. However, I completely understand where you are coming from. I had some of the same issues until I worked with a great team who showed me the abstractions, why they are useful and how they work. If I hadn’t of worked with the team I did I would likely of still been agreeing with you. I think the biggest problem is it’s hard to understand on your own unless you are deep in to the theory. You don’t need to know the theory deeply to use the abstractions but unless someone shows you how to apply them it’s hard to discover. With that your last comment is exactly right. If you are not utilising Scala type system and other features Kotlin or Java will be better. Java is moving quick these days and Kotlin is closer to a better Java than Scala is.