That Bret keeps Dynamicland and Realtalk so closed to others while touting it as “more open than open source” is really frustrating.
I get it. Opening it up means losing control. I really appreciate the desire to specifically not share it on traditionally engineer-centric spaces like GitHub as that will skew the vision towards engineering and possibly shut out non-programmers. I even get that Dynamicland isn’t really code that can be shared anyway.
But you have to give people something more than a general description and a vague invitation to visit your space. Otherwise it isn’t really open at all.
Some ideas:
- A document for how to experiment with domain exploration using tangibles and people in a way that leverages insights gleaned from Dynamicland
- A codebase for a “toy” computational system (named completely differently from Realtalk/Dynamicland so it’s clear that it is not actually part of Dynamicland) that shows how it’s possible to link physical properties to computational agents
I get it. Opening it up means losing control. I really appreciate the desire to specifically not share it on traditionally engineer-centric spaces like GitHub as that will skew the vision towards engineering and possibly shut out non-programmers. I even get that Dynamicland isn’t really code that can be shared anyway.
But you have to give people something more than a general description and a vague invitation to visit your space. Otherwise it isn’t really open at all.
Some ideas:
- A document for how to experiment with domain exploration using tangibles and people in a way that leverages insights gleaned from Dynamicland
- A codebase for a “toy” computational system (named completely differently from Realtalk/Dynamicland so it’s clear that it is not actually part of Dynamicland) that shows how it’s possible to link physical properties to computational agents