4 ms·
This is outside my area of expertise, but the post sounds like it’s asking for “choreographic programming”, where you can write an algorithm in a single functio
by gklitt 2y ago
This is outside my area of expertise, but the post sounds like it’s asking for “choreographic programming”, where you can write an algorithm in a single function while reasoning explicitly about how it gets distributed:
https://en.m.wikipedia.org/wiki/Choreographic_programming https://en.m.wikipedia.org/wiki/Choreographic_programming
I’m curious to what extent the work in that area meets the need.
- shadaj 2y agoYou caught me! That's what my next post is about :)
- ashton314 2y agoI see from your bio that you are a PhD student. What are you doing with choreographies? (I’m in this space too.)
- lachlan_gray 2y agoThis could be a fun example to work with :p https://en.m.wikipedia.org/wiki/Shakespeare_Programming_Language https://en.m.wikipedia.org/wiki/Shakespeare_Programming_Lang...
- shadaj 2y agoYou might enjoy my first ever blog post from ~10 years ago, when I first learned about distributed systems: https://www.shadaj.me/writing/romeo-juliet-and-reactive-programming https://www.shadaj.me/writing/romeo-juliet-and-reactive-prog...
- roadbuster 2y agoHow does "choreographic programming" differ from the actor model?
- LegionMammal978 2y agoFrom what I can tell, the important distinction is that all actors (and their messages) are described alongside each other, instead of being described separately. There are many implementations of the actor model, but most of them are the 'static-location architectures' that TFA talks about.