I have found Excel deeply awesome to use, and I am building a reactive programming language inspired by the concepts (for board games!).
The key is that a single script defines the entire workbook's logic, then data sits externally within a giant JSON object.
I'm trying to find a balance between the engineering concepts (source control, data versioning, audit logs) and productivity (how easy is the language and related tools).
I'm currently working on a editor for board games where I get playful with how to build UIs for the language. It's fun, but I'm wondering if I am re-inventing hypercard.
The key is that a single script defines the entire workbook's logic, then data sits externally within a giant JSON object.
I'm trying to find a balance between the engineering concepts (source control, data versioning, audit logs) and productivity (how easy is the language and related tools).
I'm currently working on a editor for board games where I get playful with how to build UIs for the language. It's fun, but I'm wondering if I am re-inventing hypercard.
http://www.adama-lang.org/docs/why-being-lazy-is-key
One mental model is that the entire document is just an Excel sheet that you can send messages to and learn of updates reactively.
http://www.adama-lang.org/docs/reference-reactive-formulas