alt Hacker NewsIt pains me to say, but it's probably too little, too late. Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron.
And now after several years of complete stagnation, the supposed improvement is a database format to fix their technical issues, so I can no longer keep all my data as markdown files? At a time when half the edits are done by Claude and tracked with jujustu, this is just not useful for me.
All I wanted was the original vision, but with less bugs and more quality of life features.
Replies
I love the concept of logseq, but the userbase is just too small and in turn the speed of change is too slow. .
Over the last few weeks, with the help of Claude Code I've finally been able to dive into Obsidian and build out the second brain I've always wanted. With the power to auto-sort small thoughts jotted down on my phone with minimal interruption and some automated maintenance & sorting.
CC has really reduced the friction to getting started with Obsidian that's held me back for years.
Sadly, these are my thoughts as well. I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as possible. Not being able to use Claude or codex anymore to write or update pages is a real deal breaker for me.
Does anyone know of a fork a version one that plans to continue?
I still use Logseq and conceptually it’s still a great method for building a second brain. It fits the way my brain works.
But it has been dormant for years and early attempts at syncing didn’t work well. I paid to support the sync effort but we saw nothing for years. That’s a painfully long time.
Yeah I felt the same about the decision when they decided to move to database structure. If it had this structure from the start it could've built up an ecosystem like Obsidian's but now it's hard to justify going for it.
I became so old waiting for usable non-lazy loading for long form notes that I ended up using Emacs for everything
i begrudgingly switched from logseq to obsidian.
I wanted to use Logseq to replace NotePlan's workflow on Linux, but it's nowhere close that. What's worse, I was barely able to setup something remotely close with Obsidian.
I agree, I truly love logseq as it fits the way my brain works in a way the few other tools seem to be able to replicate. Unfortunately my notes being in plain text is a non-negotiable for me. This will probably be the push I need to transition over fully to org-roam. My logseq files are already stored in org format anyway.