I'm not sure if you're asking whether micasa should use a text file as its format, or if you're suggesting that a text file can be a substitute for micasa.

▲

amelius 3 hours ago | parent [-]

The latter.

I do things in my house too infrequently that I don't want to have to re-learn the UI of a tool again and again.

But maybe I'm not the target audience.

	▲	cpcloud 2 hours ago \| parent [-]
		I often find myself wanting answers to questions that require linking data, and I also want to codify those links somehow, so a single-file, row-oriented database seemed like the appropriate way to get that. You might actually be able to get away with less structure and just dumps thoughts and ideas, statuses, and documents into $AI and have it generate ad-hoc reports. In which case, a text file might be the right interface. Kind of a non-answer, I realize. I suppose the answer is: because I had a relatively specific idea of what I wanted to build and I didn't consider not building it.