Is Logseq dead?

Questions & Help
1

I’m a Logseq user for a year now and I love it. However, I haven’t seen any improvements for a while now (last update April 23) and I think it’s strange for a software in beta (if I’m not wrong, they got funding). Also, the promised sync feature never arrives. So I’m starting to think that this project has serious problems or is dead. Does anyone have any information about it? If that’s the real status of the project, maybe it’s time to look for another alternative.

1 Like
2

Hi there

There are several threads about the level of development activity in the forum, which both:

  • would have resolved your concern
  • show how it is a recurring concern

To summarize, development has focused on the database version: GitHub - logseq/logseq at feat/db.

I am not sure what you mean by the promised sync feature never arrives. A Sync feature exists: How to Setup and Use Logseq Sync

5 Likes
3

To add another user’s perspective to etc’s answer:

  • I’m also kinda alarmed at how long Logseq has gone without significant improvements. There’s a mind-boggling amount of work being done on the feat/db branch, basically rewriting large amounts of Logseq’s internals to store content in a DB format rather than using plaintext markdown files as the source of truth, rewrite sync logic to be massively faster, etc. As of a month ago (??) I understand that this rewrite has been released as private alpha and is deep into testing & bugfixing territory. But it also seems this rewrite has taken substantially longer than was hoped & planned.
  • etc is right that a sync feature exists since over a year ago, however, I and many others find it unusably slow (and a bit buggy, at least for me). Enough so that I’ve given up on syncing content to my phone, because anytime I open Logseq it takes over a minute before sync is complete and the UI is usable. So I’m holding out for the DB rewrite and sync improvements to be merged, and hoping that Logseq will become “fully usable” to me at that point, rather than “halfway usable” as it is to me now.
4 Likes
4

Don’t get me wrong, this is just my perception as an external user (and it seems I’m not the only one) but I’m not saying that this is the reality. That’s why I’m asking. If many improvements are on the way, I’m very happy about it because I love Logseq.

PS.
If you allow a suggestion from someone who has worked for a few years in a software company, Github is only useful for developers or enthusiasts. The average user will never read the log to see what’s going on because he/she doesn’t understand it or he/she doesn’t care. In my case, I looked for the information about the updates on the website.

5 Likes
5

Well, I’m a ‘database guy’ can I help out in any way? I’m under-employed for now, and I would love to find out more about your product. Hit me up any time (am I allowed to provide my own PII here, or can someone reach out?)

1 Like
6

I sometimes feel the same concern, and sincerely it is not. It would be a great loss for humanity, and I mean it. Perhaps it is suffering from an extreme architectural rework. A thoughtful communication from the dev team about their roadmaps and vision would be very helpful to stay calm.
With love, a Logseq fan!!
:slight_smile:

1 Like
7

I recommend you read Why the database version and how it's going? and check the roadmap Trello

1 Like
8

I think you are absolutely right. Logseq has long made it’s way from a insider-tool to a tool used by the broader mass of people. Therefore information must (in a condensed form) be delivered in a easy to digest fashion. Not Github or discord but the main website, this forum maybe, or even youtube. Bas on the ToolsonTech YT channel does a great job of bringing logseq news and updates alive in an entertaining manner, so you might wanna have a look there.

1 Like
9

I just started using Logseq and was wondering the same.
The Blog is quiet for >1 year, while being very active before.
Latest release is from April, again with frequent releases before that.

So for a moment, I was wondering if I should instead start with Obsidian, before being locked in too much.

It indeed conincides with the DB/RTC work.
That works sounds great for the future. So I’m a little relieved now.

I guess my only worry is that there will still be a free way to sync files between platforms (via e.g. iCloud).
That was one of my criteria to pick Logseq and would be a bummer if it stops working or if I’d have to get a subscription.
I generally don’t mind paying for great software. However, I’m just a small personal user and would probably look around for free options if sync stops working.

Looking forward to try the DB version once ready!
Good luck with the progress!

4 Likes
10

I thought Markdown files being the source of truth was one of the desirable features of LogSeq.

I’m doing my own sync which is essentially to use git to sync with a remote on a server, so that I can work on either my laptop or my desktop system. I’m not using a mobile device at the moment and don’t have plans to (phone/tablet). This seems to work fine for me in the meantime. Since the data is in Markdown files, this works fine.

Admittedly, I am not a power user of LogSeq. Essentially, just keeping notes on things and linking the concepts as a 2nd brain.

11
  • The current incarnation of Logseq is pretty much abandonware.
  • The development of the current version has saturated and Logseq can not be any faster or safer without changing its core.
  • The new version is being re-built from ground up and will be much better.
  • A graph database functions as a “source of truth” just fine.
  • The new version will not be out for at least another year.
12

Can any or all of this be officially confirmed or is it secret knowledge? Or just secret de Polichinelle?

13
  • The current incarnation of Logseq is pretty much abandonware.

No. The so called Logseq DB can run both in MD and DB mode.

  • The development of the current version has saturated and Logseq cannot be any faster or safer without changing its core.

performing a graph with MD files as storage has been proven challenging. So, if you optimize your use case around some of the limitation, you have a pleasant time with the app. There are several examples of heavier use cases out there of the MD version. Else, you could potentially go in DB mode where many of the shortcoming will be addressed

  • The new version is being re-built from ground up and will be much better.

not entirely true, the MD and the DB are the same App. The DB mode branches out of the MD. Many of the core functionalities are the same between MD and DB

  • A graph database functions as a “source of truth” just fine.

the graph portion of the app remains the same. But there have been some iterations on the schema

  • The new version will not be out for at least another year.

Per my estimation, Beta in a couple of months, and out of Beta in => 12 months. They have significantly improved the development pipeline, the Testing process, with more automation integration workflow. There is a lot of changes they push each week.

I hope this help clarify a bit.

1 Like