Re: One vs many directories

[Texas Cyberthal <texas.cyberthal@gmail.com>]

Hi Jean,

> By using the Meta Org File user automatically creates an index of filed files and can search for the file in the Org file itself and open the file from the Meta Org File without knowing where the file is really located.

Such a set of links could easily grow out of date if paths change, and
I wouldn't want to maintain it.  If the paths never change, then I
would memorize the paths and linking them would be slower than Dired
walking to them.

I do have a method called "Zinks" for managing UID links.  It permits
paths to change without breaking anything, both target and source.
However, in the vast majority of cases I find it much easier to just
walk the directory tree.  I doubt one can appreciate how useful a tree
synced to one's mind is until one has experienced it.  The tree adapts
to the mind and vice versa.

There's no need to know the exact locations of files; walking there is
informative and useful.  Or, for the trivial paths, walking is so
quick that it is faster than searching.  Search spawns distracting
mismatches to read, whereas walking the tree progressively narrows
scope in a mentally comfortable way that focuses the mind while
error-checking each step.  It's very comfortable to reach the
destination and be confident from the process that I'm in the right
place.

> File system is database.

Barely.  Databaseness is a gradient with file system at one end and
PostGres at the other.

Plain text and file system are the computing foundation.  The largest
and best set of tools apply.  Departing from them loses much.

A filesystem is extremely ergonomic with the right tools, and handles
bulk data very well.  Any database, even Org's, has higher overhead.

I do intend to integrate databases into Cyborganize with Dbmind, but
have barely thought about it yet.  Cyborganize should run fine without
any database, but of course database is extremely useful for business
etc.

I just don't think paths need to be input into the database.  The
strength of the database is freedom from the file system.  It should
focus on the things a file system can't do.  For example, querying all
the people who work at X company, or who live in Y country.

Duplicate Org IDs aren't a problem in my experience.  Noticing their
existence is a good way to reconcile the split after the dust of
execution has settled.  An Org workflow shouldn't generate lots of
duplicate links.  One that does probably indicates overuse of both
links and heading duplication.  If one really does need lots of unique
IDs, it's probably a sign to move to a heavier database than Org.

I'll fix that link.  The correct URL is
https://github.com/cyberthal/Textmind-template

Glad to hear you're finding Cyborganize components useful.