Linux system manufacturer System76 introduced a beautiful looking Linux distribution called Pop!_OS. But is Pop OS worth an install? Read the Pop OS review and find out yourself.
Zim notebooks consist of plain text files (.txt extension), with sub-pages stored in subdirectories. So, say you have a TODO page, and beneath that, "Work" and "Hhome" pages. On the filesystem you'll have "TODO.txt", "TODO/Work.txt" and "TODO/Home.txt", with each file being human-readable. Zim files have a 3 line header, similar to HTTP headers with three entries: Content-Type, Wiki-Format, and Creation-Date. After that is the file body, which is plaintext human-readable conventions for formatting, as documented here [zim-wiki.org] and also available within Zim itself.
Which is to say, it's very amenable to version control systems because it's all plaintext. The only exception is, if you choose to attach a binary file to a page (either by adding an image to a page or using the "attach external file" option), you get the usual caveats with binary files and VCS. That and the general human-readability of it make it appealing to me, because I hate locking important info into non-standard formats. If Zim ever breaks or stops being maintained, my data is still readable, and it should be simple enough to make a parser for it if I ever need. :D
(Score: 2) by Marand on Wednesday January 17 2018, @04:23AM
Zim notebooks consist of plain text files (.txt extension), with sub-pages stored in subdirectories. So, say you have a TODO page, and beneath that, "Work" and "Hhome" pages. On the filesystem you'll have "TODO.txt", "TODO/Work.txt" and "TODO/Home.txt", with each file being human-readable. Zim files have a 3 line header, similar to HTTP headers with three entries: Content-Type, Wiki-Format, and Creation-Date. After that is the file body, which is plaintext human-readable conventions for formatting, as documented here [zim-wiki.org] and also available within Zim itself.
Which is to say, it's very amenable to version control systems because it's all plaintext. The only exception is, if you choose to attach a binary file to a page (either by adding an image to a page or using the "attach external file" option), you get the usual caveats with binary files and VCS. That and the general human-readability of it make it appealing to me, because I hate locking important info into non-standard formats. If Zim ever breaks or stops being maintained, my data is still readable, and it should be simple enough to make a parser for it if I ever need. :D