At TPAC in 2017, someone asked me, what would I do if I could work on what I was really interested in and cared about? I sheepishly admitted that, well, I'd like to work on social networks as a distributed virtual world / game.

I thought I'd be laughed out of the room. Instead, it turned out that almost everyone I was working with had background in that space. Even the ocap stuff I'd been studying came largely from Electric Communities Habitat.

That gave me the courage to pursue #Spritely.

@cwebber Just got my first awareness of Spritely.

Looked fun until I saw you're using Racket. Then it looked *really* fun!

@ptvirgo I'm glad you're excited! The first independently runnable demo is available, and I think it's also very readable Racket code:


@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.

Sign in to participate in the conversation
Mastodon for Tech Folks

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!