Have any of you tried switching to logseq? why / why not?
Have any of you tried switching to logseq? why / why not?
I tried Obsidian but ultimately landed on Logseq. The short version is that the workflow with Logseq is very block-focused rather than page focused. Your organization can be more organic; following tags and links rather page/hierarchy. Finally, Logseq wasn't getting in the way of me using it for work. Obsidian's license model made my situation... murky.
That said they are not mutually exclusive. Plants if folks use both. Obsidian's experience is much better for deeper subjects focusing on a specific page. Logseq is much more block focused.
Logseq is also not without it's flaws. The app can be super slow in large graphs, and they are rewriting the backend so feature development is at a near standstill right now. No collaboration features and a shakey business model makes it hard for me to recommend hard.
TL;DR: Logseq is more capture and block focused. It's worth checking out but hard to recommend for everyone.
6That sounds like it might be pretty great for me actually I will check it out for sure. Do you know if it’s possible to just import an obsidian vault into logseq? If I could just make it an easy migration it might be great
3Actually yes! You may need to do some fiddling but it is possible. I didn't do that so I didn't have a tutorial handy but the Logseq forums have many posts on sharing the data between the two long term. Might be worth a look
2
I never tried obsidian because it's not FOSS. Have been exploring logseq which isn't a direct replacement but it's good enough for my purposes
2If it weren't electron-based, I might have stuck to it but, that's a deal breaker for me. The non-FOSS-ness of Obsidian is also a deal breaker. So, I'm just in neovim for notes until I find or make something better.
1