![]() ![]() (I’m on the fence about Obsidian, since it’s not FOSS). I plan on keeping Logseq and Zettlr on my system indefinitely. So, if I do want to see a network graph of my notes, I could fire up Logseq and take a look. All three promise not to lock me in, and they are true to their word.īecause they’re built on top of simple text files, I can simply jump from Zettlr to Logseq to Obsidian, adding new notes to my collection, and not have the underlying file structure be damaged in any way. However, while I’m using and enjoying Zettlr, the real power of all of these systems is that I don’t have to choose. I’m really happy to be able to write like this while I write about FOSS. So, with Zettlr in the mix, I use FOSS across the board, from my underlying OS (various Linux flavors) to Firefox to Zotero to Zettlr to Libreoffice to this blog. Obsidian, however, is not, and does not appear to be going in that direction. Since I’m adopting the pose of the FOSS Academic – and since Goal 2 of this blog is to write a book about FOSS – I really have to choose it. The Workspaces layout reminds me of good text editors, the autocomplete on links works quite well, and the right-hand sidebar gives me all the information I need.īut the biggest reason I’m choosing Zettlr is that it’s FOSS. So instead, I’ve opted for the one with the most comfortable interface, and that is Zettlr. The differences appear in how they show those links to me – Obsidian and Logseq show network graphs, and Zettlr just shows backlinks.Īs much I think the graphs are cool, I don’t really see much value in them in my day-to-day. They also allow for easy octothorpe (#) tagging. What was missing in the middle – the Markdown phase – was linking between notes as well as tagging, which is why I’m trying out Obsidian/Zettlr/Logseq in the first place.Īll three of them do wiki-style linking between Markdown files. I take notes on things in Zotero, I jot down thoughts in Markdown (previously in the aforementioned RedNoteBook), and then I synthesize the lot in Libreoffice with the Zotero plugin. If you start searching those terms, be prepared for lengthy manifestos about how to take notes.Īs for me, I guess I’m keeping it simple. As its name implies, Zettlr is inspired by the “Zettlekasten” method of Niklas Luhmann. Logseq is based on “block-level” linking, which itself builds on RemNote. Obsidian in particular has a lot of fans on Youtube (e.g., this video), who share their complex workflows and talk about how network graphs reveal new ways of thinking. Moreover, I get the sense that all of them have some very zealous adherents. I thought about writing up comparisons between these systems, but I think those sorts of posts abound – just DuckDuckGo “obsidian vs zettlr” or “zettlr vs logseq” and you’ll see what I mean. In fact, I have all three installed and may hop between them. However, given what these projects are doing, I do not feel locked into my choice. ![]() It meets my needs quite well, which are probably a bit more minimal than people might expect. So, I have tried both Zettlr and Obsidian – and I also tried a third system, Logseq – and have decided to adopt Zettlr. I was hoping to streamline blogging, note-taking, and other Markdown tasks in one system. I use it regularly to plan my weeks, I obviously use it for this blog (which is a static Jekyll site), and I started using it to jot down ideas in a journaling program called RedNoteBook. I asked because I’m using Markdown more and more. Both are Markdown editors which also provide valuable features on top, including linking together Markdown notes and varying degrees of Zotero support. ![]() About a week ago, I took to my home Mastodon instance, scholar.social, and asked whether people preferred Zettlr or Obsidian. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |