I am into this. And we are not alone. There this failed demo about a company letting “designers” as in “graphical designers” push to production from a convo within the IDE. Some people are experimenting with similar workflow but working from discord / slack.
That, in my humble opinion, what happens in Möbius. Each one has its own workbench, and there is a shared space, but none can overload existing work (it is append only), and “fork” have an history, a lineage. I wonder whether that is what you had in mind with “equal peer relation”?
I created a prototype notebook-like app, where I can create, embed and debug applications on-the-fly in the conversation:
There is step, big or small, to turn that into a plugin for discourse, but I can imagine / dream a code path toward that goal.
When I started working on Möbius I had the idea of using a concatenative language, but the requirement to also have every identifier translatable broke the “design”, so I fallback to non-concatenative language. I mention this, because the problem of the prototype in the above screenshot is the almost complete absence of agency code-wise [0]. Change in micro-apps can only be done via natural language. My goal is / was to let the user “open the (generated) clicker game source” and edit it directly, an inspector and commit it in the shared space, and let people look at the work-in-progress process, and the result.
[0] editing python and json soup of pseudo html in a notebook is not something find malleable.
