3 ms·
For me, it seems that liveness and literacy are in some tension because liveness allows acting without the intent of producing a document and literacy facilitat
by brudgers 9y ago
For me, it seems that liveness and literacy are in some tension because liveness allows acting without the intent of producing a document and literacy facilitates an intent to produce a document.
I think the tension may revolve around scope. For example, liveness allowing a document's text to be translated from Hebrew to English seems more likely to be consistent with the an author's intent. Liveness that allows changing "In the beginning" to "Check out my new website" seems less likely to be so. The tension is that the scope of liveness which is appropriate in a particular case will vary. An author may want to allow the transformation to "check out my new website" but not "The future is already here."
In a truly live system, the rules for what is and isn't alive would also be alive. It's turtles all the way down...until you get to StackOverflow or something something static. The tension, at least for me is that the system has to decide where the liveness stops and like abstractions, adding one more layer of liveness is always attractive to a systems architect.
The alternative where liveness is added by the author and things default to dead may be better for many use cases and perhaps what is needed are better tools for adding liveness. Some of the use cases I am thinking about are situations in the same class as an Excel spreadsheet executing malware. Part of what makes this plausible to me is that this --interactivity enabled explicitly by the intersection of author and reader permissions -- is the way Emacs org-mode works. And org-mode is relevant to this particular video because it was used to prepare the interactive presentation {mentioned somewhere between 40:00-45:00 in the video}.
- gbracha 9y agoI agree that there are times where you want to nail things down so they cannot be changed. It's just that it's easier to restrict the behavior of a live system than to customize a "dead" one. Hence liveness needs to be at the foundation.
- brudgers 9y agoI had not yet listened to the QA portion of the talk when I wrote my comment, so maybe I did not entirely account for how much my take might have been a response to what was said for effect...and now I have also had a bit of time away from my comment to think a bit more. Openness may be a third axis that relates the design of platforms/systems intended for liveness and literacy. A sketch of contrasting approaches to openness might be between Emacs and a traditional Smalltalk IDE. Emacs is open in the sense that the designers designed the tool around user customization and extension. Smalltalk IDE's tend not to have that as a first order design principle. Over the long haul (openness in Smalltalk seems to happen at a different layer of abstraction). I think it may be more practical to add liveness to a programming tool with openness as a primary design goal than openness to a programming tool with liveness as a primary design goal (with the premise that openness is not also a primary design goal of a particular programming tool).