>Isn't this article just stating the obvious fact that programs at some point do I/O, so no program can be purely functional? I agree with the point that a pro

>Isn't this article just stating the obvious fact that programs at some point do I/O, so no program can be purely functional? I agree with the point that a program can't be purely functional, but lately I've been wondering if you could still have a programming language that is purely functional (preferably also total). It is designed for writing data transformation libraries and needs to be called into by a stateful language that handles IO and orchestration. If you've seen Gary Bernhardt's talk Boundariers [1], this language would be the purely functional core. [1] https://www.destroyallsoftware.com/talks/boundaries https://www.destroyallsoftware.com/talks/boundaries