dagipflihax0r

Mangle https://github.com/google/mangle is an open-source implementation in golang, it was an explicit goal to make it easy to learn. Meaning: it is easy to recognize the pure datalog part, the syntax is following the good old course material.

It was discussed here: https://news.ycombinator.com/item?id=33756800

see also: "Software Engineering at Google: Lessons Learned from Programming Over Time" 1st Edition by Titus Winters (Author), Tom Manshreck (Author), Hyrum Wright (Author) O'Reilly

It may help to know that "[computational] effect" is supposed to mean these things together: - a particular class of computation, in a programming context where we want to define the class and/or take advantage of computations being defined in this way - to this end computations are wrapped in a type constructor (typically with one argument e.g. State<T>, IO<T>, Maybe<T>).

The jargon is of course terrible and unhelpful (but widely used and used somewhat consistently). It is not necessarily about side-effects, it is not necessarily about interacting with environment. Calling it "algebraic effects" makes it a bit mysterious the various supported methods/callbacks are more or less like an "algebra", since they involve the type parameter T. To top it off, this use of "effect" is quite different from, say "type and effect system", and Moggi's 1991 never used "effect" in "Notions of computation and monads."

It's a lot of words. People who cannot explain things well tend to use a lot of words.

The author cannot explain things well. You just witnessed the art of abduction!

(Just kidding. It's worth knowing what abduction is and recognizing it.)

That would require garbage collection support, no? To me (very limited) knowledge, supporting gc in WASM is being worked on but not there yet.

I think Yanis Smaragdakis Onward! 2019 paper fits here "Next-paradigm programming languages: what will they look like and what changes will they bring?" https://yanniss.github.io/next-paradigm-onward19.pdf

He has done a lot of work using datalog and argues, convincingly in my opinion, that it is reasonable that some of the elements of datalog-like programming will be part of the future. For example, that there is a very simple way to express a relational-join and the underlying machinery figures out the most efficient way to do it, just like a DB query optimizer does.