I love French computing terms.
A program is a logiciel (from logique + -iel, by analogy with and opposition to matรฉriel), and an OS is a systรจme d'exploitation.
@liquidprismata Not sure what you mean "you want achievement without achieving".
I want to liberate people from having little to no choice or agency in how they may compute and interface with technology and each other through technology.
@liquidprismata I would prefer to not be forced to interface with anything without my consent, naive as that may sound. But if I must, under threat of force, I would at least prefer to do so under more flexible terms.
The entire "office" metaphor of computing has outlived its purpose. Files, folders, desktops, etc.
Now is the time to rebuild computing from the ground up with relationships as the primitive.
OpenDoc correctly observed that the contents of documents are opaque to the OS and lack composability.
Its answer was to give documents more structure from the top down.
A hypothetical bottom up alternative: make the filesystem so powerful that documents aren't needed anymore.
I want to debunk the claim that I see a lot around here that Obsidian is "just plain text markdown files" which means "you can take them anywhere and open them with any app"
That simply isn't true
Yes, maybe the raw text of the notes is markdown, but many other parts cannot be moved elsewhere and opened by other apps:
1. The .obsidian/ directory contains your JSON config with plugins, settings, hotkeys, workspace state, link format, attachment paths โ those can't be moved elsewhere
2. Plugin state files โ Readwise's path-to-ID map, Templater's settings, Tasks plugin's database, Excalidraw's drawing data โ even if plugins can be recreated, these settings cannot
3. .canvas files โ JSON, not markdown. They reference notes by path and won't survive a move
4. .base files โ JSON-based database/views over your notes. Same path-fragility
5. .excalidraw.md files โ markdown wrapper around an Excalidraw JSON blob. Looks like markdown, isn't really
6. The link graph itself โ backlinks, graph view, "linked mentions" โ all computed from filenames and link references. They survive because the references are in the markdown, but they require Obsidian (or an Obsidian-aware tool) to materialize
7. Plugin-managed folders โ Readwise output, Web Clipper output, Daily Notes location, Templates folder. Each is a folder whose contents are owned by an external system tracked in plugin state
8. Sync state โ Obsidian Sync, iCloud, Dropbox, Google Drive each maintain their own state about what's where and what's been resolved. Move operations interfere with this state
9. Embedded query results โ Dataview queries, Tasks queries, Bases queries. The query is in the markdown; the result is computed live and never persisted
So technically you CAN move your files elsewhere, but you'd destroy most of what makes them valuable โ the graph, the plugin state, the canvases, the embedded queries, the sync state, and any structural intent encoded in folder placement
Which means you're just as locked in to Obsidian as any other "proprietary" app, it's just a hidden lock-in that's obscured by inaccurate marketing
Saying "Obsidian is just markdown files" is like saying "your house is just bricks"
The bricks are real and moveable โ but the architecture, plumbing, and wiring aren't bricks, and those are most of what makes the house function
There is so much potential in AI coding... man... we gotta get serious about this shit. Insane things might happen soon. Fully cross-platform app development. Much more flexible UI -- a totally different shape for apps.
Your kids will love this video!
Grok Imagine prompt:
The kittens with mittens start dancing and singing โweโre kittens with mittensโ with joyful, energetic movements and playful expressions.