> Well because you need the rest of the language to make your program tell your system to do stuff.
That's not necessary for business logic, though. This would presumably be embedded in infrastructure that handled i/o separately.
That's not necessary for business logic, though. This would presumably be embedded in infrastructure that handled i/o separately.
Haskell, to some extent, can help you structure your program in this way where the business logic is just simple, plain, old functional code. You can write the data marshalling, logging, and networking layers separately. There are a few ways to tackle that in Haskell in varying levels of complexity as you would expect coming from other general-purpose programming languages.