> there's a transition towards using a database instead of the filesystem
Looks like it won't transition away from using the filesystem though:
> […] we’ll continue to support both file-based and database-based graphs, with a long-term goal of achieving seamless two-way sync between the database and markdown files. This will allow you to leverage the benefits of the database version while still being able to use other tools.[1]
An important warning. Logseq is very nice for some things...until it loses your data. You know you put something into Logseq, but it's not there, so you question if you're losing your mind. That's one reason they're switching to a database.
I'm also hesitant to rely on Logseq for another reason. They've taken a lot of funding and now they're in the monetization phase. When I asked about the status of the open source project on Github, the response was crickets.
Full. agree on the data loss issue. I have experienced it myself, and their forum and issue tracker also show this. Its not a « trusted system » at all.
My main note tool for years has been Obsidian (using Obsidian Sync on Linux, Windows, Android, and iPhone). Works great for regular notes.
I don't think it's very good as an outliner, though I haven't tried the recent outliner plugins, so maybe things have improved. I do my outlining with org-mode on Emacs because of my dissatisfaction with Obsidian in that area and lost data on Logseq.
I have been a daily logseq user for at least a couple years now, and I have not had a problem with my data being lost. I have heard of people having this issue with Synching - which I am also using - but I haven't had issues.
I like how the data storage is markdown files. I love the block centered outlier approach and use block references extensively.
I've developed some extensions too. The documentation is severely lacking here, but there are enough extensions on the (currently free and oss) marketplace that can be useful examples.
The query language is really freaking weird to me. It's clojure, datascript/datom. Not intuitive at all, but I've got several custom queries working as part of my workflow.
Overall Logseq is good software and I'd recommend it. Certainly take backups - I have from the start because of experiences like the above - but I haven't needed them yet.
I used logseq for about a year and I so hate the block-based editor (the same reason I stopped using Notion). I went back to using flat-file for a while until I find Zettlr.
As an outliner, and being block-based, I think it's more suitable for Zettelkasten and generally atomic notes.
Progress on the `master` branch is a bit slow because there's a transition towards using a database instead of the filesystem https://github.com/logseq/logseq/tree/feat/db
https://discuss.logseq.com/t/why-the-database-version-and-ho...