@cwebber Nice, I'm checking it out.
Do you have a favorite tutorial on the actor model? My background is pretty non-traditional, though I've been fleshing things out.
@ptvirgo I don't have one, I'd like to write one though. It's pretty simple: think of each actor as an entity with some address you can send messages to, which can also potentially spawn actors itself, which can send messages to the other actors it knows about, and which can change its state or behavior in response to messages.
Here's a hint: actors are objects, but asynchronous. Handling messages tends to be like method dispatch. :)
@cwebber Thanks for the hint .. ! Sounds like a simple idea that gets really powerful when applied well. I'll poke around a bit and see if I catch a light-bulb.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
We adhere to an adapted version of the TootCat Code of Conduct and follow the Toot Café list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators.
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!