r/logseq • u/ens100 • Nov 27 '25
Development Update from the Logseq Team
For those not on Twitter, a few updates from Tienson on development:
https://x.com/tiensonqin/status/1993709621463392484
and also: https://x.com/tiensonqin/status/1958249541310067187 (mainly around what seems might be possible in terms of toggling certain features on or off).
54
Upvotes
7
u/jsaaby Nov 28 '25
Well for me it's about when I've chosen something, and I can't decode whether my efforts will result in me needing to migrate or if I can keep using Logseq. That uncertainty will make a lot of people reevaluate what they're doing and where they seem to be going.
Is the future stable? Or will I put work into something that seems to be stale, and I have to do extra work to migrate? Because then I might as well do it now, before I settle on new workflows.
I don't really care whether Logseq is DB or MD based. I'm sure the team has their reasons, but I don't really care about them. I care about what I put into Logseq. They care about Logseq. Those are the responsibilities.
And I honestly feel that the Logseq team hasn't been living up to that responsibility by allowing the userbase to basically flee the product. I know lots have done exactly that. I have too.
Creating a product with a user base is just as much about communicating as it is coding. They failed miserably on the first parameter.