💡 Change graph as main interaction point to make history discoverable.
We were busy this week exploring concepts for the Lix File Manager, guided by the question: How can a user observe changes?
Answer: The change graph.
The change graph helps the lix user navigate through history of their files.
Insights:
- Users benefit from multiple, filterable graph views. Expectations differ between Lix & file scope.
- Being able to connect discussions & tags to every change makes the system super flexible
Full steam ahead 🚂
1. We shifted the primary focus from @inlangHQ to lix.
2. We are re-building lix on SQLite instead of git.
The result is more perceivable progress over the last 8 weeks than 24 months combined 🚀
my head is exploding with implementing efficient branching on a disconnected change graph.
- O(total entities * number of branches) is too expensive
- "branch points" could be a solution
