undefined | Better HN

0 pointskazinator9y ago0 comments

State is something that is best just embraced rather than "dealt with".

0 comments

3 comments · 1 top-level

bbcbasic9y ago· 2 in thread

An analogy to that is that OO doesn't embrace IO. Yet weirdly enough that makes OO-IO better than older languages that have built in commands to write to disk.

Haskell doesn't have state but you have multiple models to choose from, from simple folds to STM or State or Reader or Writer Monads all of which serve different purposes and do different jobs well.

kazinatorOP9y ago

OOP absolutely embraces I/O. I/O begs to be OOP and makes, hands down, the best use case for illustrating OOP.

bbcbasic9y ago

What I am getting at is that OOP languages like C++ have no IO commands built in it is all delegated to libraries.

Haskell has no state support built in, it is all delegated to libraries.

So:

C++ has excellent IO support, but the language doesn't embrace IO at all.

Haskell has excellent State support, but the language doesn't embrace State at all.

2 more replies

j / k navigate · click thread line to collapse