Hacker News new | ask | show | jobs
by u1hcw9nx 12 days ago
CL conditions do what you actually need if you program. CL gives you deterministic state, safe resource management etc.

Nondeterminism is not a feature you want. Algebraic effects treat the execution stack (continuation) as data, you have total freedom over what you do with it. This flexibility is exactly where you get nondeterminism. This is how logic solvers or probabilistic algorithms work, but you don't want it as a programming language feature in general purpose programming language.
2 comments
oisdk 12 days ago
It’s pretty annoying to comment “this thing was already present in CL 30 years ago”, then to have someone correct you (pointing out that this is a common misconception, and algebraic effects are not equivalent to conditions at all), and then to respond not to admit you’re wrong but instead to say “algebraic effects are bad anyway because you shouldn’t want one of the extra features they give you (nondeterminism)”.

By the way, nondeterminism is not the only difference between the two.

link
u1hcw9nx 12 days ago
Standard usable feature. Features must work with everything else in the language.

I like programming language theory as much as anyone else, but there is a reason some language features exist only so that people can blog and think about them.

link
mrkeen 12 days ago
> Nondeterminism is not a feature you want.

I can get behind the sentiment, but you absolutely need nondeterminism. You can separate the d from the non-d, but only Haskellish languages even attempt it. It's a coarse separation to make (IO vs non-IO), which is where effect systems come in - I guess you can categorise code into more fine-grain buckets. The 'algebraic' part is currently beyond my knowledge.

link