alt Hacker NewsSuper cool!
I'm completely sold on the canvas layer. Embracing non linearity is such a boon when you're on the ideas stage. When you have verified it though, moving it to another medium (a document, presentation or just code) is often the best choice.
Do you see the canvases created with Spine as "one off" that you discard when you have got your deliverable, or as something living that you keep around?
I'm building a side project for running SQL on a canvas (kavla.dev), so I'm thinking about canvas workflows all the time!
Thanks! Great question. We see canvases as living workspaces, you can revisit, iterate on, and build on them over time.
But the deliverables (docs, slides, code) are first-class outputs you can export and use independently. So it works both ways depending on the workflow.
Kavla looks cool, canvas-based SQL is a great use case for this kind of thinking!