<https://www.divergent-desktop.org/blog/2020/08/10...
# thinking-together
s
g
wow this is amazing!!
s
Somewhat reminds me of https://www.mercuryos.com/
g
@Kartik Agaram for some subconscious reason, Principle 11: Defer Composition reminds me of your project
👍 1
s
I hope that the future of software is more about interoperability and context-aware flows (both of which are essentially absent in todays products due to the desktop paradigm and web page paradigm). It’s as if every app/company needs to become it’s own bespoke marketplace and spread very horizontally with it’s feature set to accommodate edge cases. I see a future where the democratization of “features” broken down into smaller units and the new operating system, like Mercury for example, is the binding agent by applying some, if not all, the principles outlined in that wonderful article.
👍 2
k
@Garth Goldwater I don't understand why, but I'll take it 😆 It reminds me more of Alan Kay on late binding.
g
i think i was thinking about you pointing out that you didn’t actually need to use ncurses. sounded like a similar kind of situation emerging from your prototyping
👍 1
k
Yeah that makes sense. I hope to one day reach his desired state: add graphics, subtract terminal escape sequences.
Persistent state stores should not be some assumed default, but rather require interactive/user-initiated automation. Lifespace should be coupled to namespace.
I ❤️ this much more than @François-René Rideau's ideal of orthogonal persistence: https://ngnghm.github.io/blog/2015/08/03/chapter-2-save-our-souls. Yes, the two are not mutually exclusive. But they are both hard, and they point us in opposite directions. If I had to choose one, I know which way I'd go.