2) Of course, copy paste can get out of hand quickly. But the demo shows a smart environment where provenance is tracked when you copy-paste, so changes can be propagated between copies as things change.
Great example of the potential of moving beyond dumb text editors.
A fun additional connection: spreadsheets are projectional editors.
Many spreadsheets use relative coordinates internally. You type "A1" but it stores "Left by 2 cells". As you copy-paste the formula, keeps the same relative ref, but points to a different concrete cell each time
The key is that the editor is rich enough to show you some useful projection of the literal internal state.
Similar dynamic in Jonathan's demo as with many projectional editors: because it's not just editing a raw plaintext representation, can do various useful things
• • •
Missing some Tweet in this thread? You can try to
force a refresh
In the early 90s, there was a lot of hype about "component-based software" -- editing different parts of a document with different mini-editors.
Why didn't it catch on? 7 theories I've come across:
1) UX quality. If every component is developed by an independent company, who is responsible for unifying it into a nice holistic experience rather than a mishmash?
2) Modality. Different parts of your document operate with different behaviors. How does the user keep track?
The problems described in this OpenDoc video are still so relevant, 30 years later.
"Developers pile on feature after feature. The result is large monolithic applications. Data rich content is hard to share across applications..."
Each cloud its own pyramid, with scarce bridges in between...
Dreaming of a new OpenDoc...
- Little components, each responsible for editing part of a document
- all data stored on a shared user-controlled substrate, not split across clouds. the filesystem is dead, long live the filesystem