I got to play with Dynamicland for a couple of hours last week, thanks to a meetup organised by Steve Krouse and Omar Rizwan. Steve runs the Future Of Coding po

I got to play with Dynamicland for a couple of hours last week, thanks to a meetup organised by Steve Krouse and Omar Rizwan. Steve runs the Future Of Coding podcast ( https://futureofcoding.org/ https://futureofcoding.org/ ) and Slack community, and Omar is a researcher at Dynamicland. Last year Omar posted an excellent, detailed breakdown of GeoKit, a map toolkit he created at Dynamicland; it includes much of the technical detail and videos you probably want if you've read this far: https://rsnous.com/posts/notes-from-dynamicland-geokit/ https://rsnous.com/posts/notes-from-dynamicland-geokit/ My own feelings about Dynamicland, after a couple of hours there, are mixed but mostly positive: * Like many who experience it, I don't have a handle on DL's most valuable differentiators as a platform. But that's OK, because it feels like they're not trying to achieve that yet; it's more about just experimenting. We're so unused to computing with this UX model that it's going to take a while to find its best uses. * Plus, DL is chasing an idea for which the hardware barely exists yet. Ideally, it would be cheaply sensing full 3D in the environment, and projecting higher contrast visuals at all angles. * Even so, there are some easy, playful ideas they've done that are wonderful. For example, an animator script which lays out three paper-sized outlines to the right of wherever you place the script, and then rapidly cycles the images it captures from those outlines. So, if you want to teach animation, you just draw a cycle across three pieces of paper, put them in the outlines, and the animation shows up instantly on the animator. * The RealTalk code for the whole DL environment is pasted on a couple of whiteboards on one side of the space. They've voluntarily chosen to constrain themselves in how complex it can be. I really like that.