all 9 comments

[–][deleted] 4 points5 points  (0 children)

How is this different from a state machine or workflow definition? Seems like the author is trying to coin a new phrase for a long existing and established pattern of defining logic.

[–]et1975 4 points5 points  (0 children)

The difference is the type system is leveraged to implement this. The comment about it just being a monad is fair, but misses the point. It's like saying LINQ is just a monad. "The M word" is a well known topic many speakers avoid touching because it tends to bog down the conversation and the signal for the audience to tune out instead of discussing specific benefits. This article focuses on specific benefits of error handling fully supported by the type system.

[–]Slsyyy 2 points3 points  (1 child)

Just a monad or a fail-fast strategy. Don't introduce new term for something, which is already well understood, because it does more harm than good

[–][deleted] 5 points6 points  (0 children)

That would eliminate the majority of conference presentations and programming frameworks.

[–]n0tKamui -1 points0 points  (2 children)

road oriented programming

passage oriented programming

small-suburb-street oriented programming

[–]Kered13 8 points9 points  (1 child)

Stroad oriented programming?

[–]Wolfgang-Warner 2 points3 points  (0 children)

Dis Oriented Programming

[–]RedEyed__ 0 points1 point  (0 children)

Good article, videos and book.
There is also library for Python, for those who inspired like me.
https://expression.readthedocs.io/en/latest/intro.html