> However (back to basics), **please** don't add "database > programmer/administrator" to the requirements of using Leo for basic > functionality - keep storage of plain text in filesystems as the base/core > data model, and the database layer as extended, optional flexibility.
I'm excited by the idea of cross-file clones and the prospect of handling multi-gigabyte data files. I'm cautious about the prospect of moving key intelligence into an opaque storage format. Yes we have number of prominent unlikely-to-ever-die open source DB platforms, however we still need special tools -- and skills -- to inspect their contents. Where is the Vim and Emacs of the DB? The humble text editor is the only tool I use today that I also used when I first started to learn computers. Correspondingly, text files are the only data which could be ported and used across all those many machines in the intervening twenty years, essentially unaltered. And I'm just a young fart. This modest quality of text is easy to overlook, part of the ground underfoot, but also of great significance, as is the ground. I'm pretty sure everyone here is cognizant of the inherent value of plain text, probably deeper than myself, but I figured I'd say this piece anyway so it's expressly part of the discussion. (And finally, my apologies to Leo for putting it in the same class as Edlin ;-) -matt -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
