There is interest from the Erlang community. Etylizer is a set-theoretic type checker developed for Erlang. We have different objectives, though, as we try to remain backwards compatible with the existing type specs. https://arxiv.org/pdf/2302.12783.pdf

It is wonderful to see so much enthusiasm about this technology. I have been working on CRDTs since 2012 and it has been quite a ride.

For those looking for more information, have a look at the information collected at http://crdt.tech/ (Disclaimer: I am involved, though Martin did the bulk load of the work.)

If you are into CRDTs for collaborative gaming, we are looking for partners and investors: https://concordant.io (Disclaimer: I am technical advisor in its team.)

Germany is running the biggest hackathon ever to fight corona. Challenges span everything, from tracking, organising material, designing tools for home office, mental health, reaching out to elderly, kids, parents, teachers ...

https://wirvsvirushackathon.org/?lang=en

Make an impact and give back!

Given the challenges list https://airtable.com/shrs71ccUVKyvLlUA/tbl6Br4W3IyPGk1jt/viw... , google translate regrettably doesn't (only the frame). Bing translate just dies. :/ The CSV request has a short and signed expiration, so that wasn't a workaround.

[Disclaimer: I am an Antidote maintainer]

Some CRDTs support garbage collection directly - if you run them in a causally consistent environment. Antidote is causally consistent and has a Set and Map implementation that work like this; for these CRDTs you don't need a global sync.

Thanks for the reply. Don't you negate some of the advantages of CRDTs by mandating casually consistent environments? Can you speak to that more?

(one of the maintainers of Antidote)

There is a lot of research still going on in the back, including indexing, access control, verification tools for apps, and some other really cool stuff.

Efficient support for queries is non-trivial, indeed.

We tried a couple of weeks back, but then most dependencies have not been upgraded yet. The problem is that, to my knowledge, there is no riak_core for Erlang 20.

I suggest that you build on top of the Riak Core from Heinz Gies. That's what we are using in some of our new projects.

This is what we actually do. I checked a couple of weeks ago with Heinz, but there wasn't a version available (but maybe I misunderstood him...).

Can you point me to an Erlang 20 compatible version?

Ah, we might be pulling a branch for our Riak Core work. I can look into it tomorrow and get back to you.