Im not really a good programmer, so is that still the case, or will database version be rewritten in something different?
If youâre not a programmer who wants to contribute to Logseq, the language in which Logseq is written is irrelevant.
There are always folks who will mention that language X is better than language Y. But for end users, it really doesnât matter what language an app is written in.
4 Likes
I just want to post a recognition to Logseqâs devs.
Sometimes we get lost in our desires and hopes and hurries. But the DB version that anyone can test online is AMAZING and the work is indeniable.
Beyond the features and requests there is a spirit and bravery to take an app and practically redo it.
Take your time to keep doing it well. Most of us will be here when the moment comes.
2 Likes
A few notes for all the people wondering when Logseq DB will be released:
There is no official timeline and I have no inside information. I have, however, been using Logseq for 4 years and have been intensively testing the DB version. So even if the team wonât say anything, I can make some educated guesses.
There are three stages: alpha, beta, release. Right now it is in a closed alpha. (NOTE: The MD version is still just a beta app. The DB release is an important step in moving Logseq past the beta stage.)
I think the switch from alpha to beta will happen fairly soon. My guess would be that it could happen sometime this spring, but whether that means March or June will depend on exactly what the teamâs internal goalposts are. Last week I had some time and imported my large graph with several thousand pages and thousands of tasks and was able to use it pretty well in the current version of the DB.
While it could still use better performance, it is good enough for me to use it daily. My big issue was with asset handling, but I understand that the desktop version of the app will fix some of my issues with assets. This was due this month, but has been delayed due to sick team members. That means, though, that the desktop app should be out in a matter of weeks.
So what are the teamâs internal goalposts are for a beta release? They havenât said. I suspect that making import foolproof would be a big one. I just wrote a post about current import limitations. Failing to do that will cause them a huge amount of headaches dealing with supporting upset users. I donât know what else they want? Real time collaboration (RTC)? (A promised new feature.) Sync? If so, it might take a bit longer to get to a public beta.
As far as the first official release (moving out of beta), they will need a decent period of beta testing to iron out bugs. Hard to tell how long? I do know, however, that they are eager to start charging for the âPROâ version (with RTC, sync, and publishing) and so they want to do this as soon as possible.
A month or two ago I was more pessimistic about the timeline, but having tested the latest version of Logseq DB I am really impressed with the progress they are making.
4 Likes
But as far as I understand, they want to deliver the beta already with the real time collaboration and with sync, which means that if we have very good luck, we can see the beta around December. I really hope youâre right tho
2 Likes
I know theyâve been testing those things internally, but I have no insight into how far along they might be. It is really impossible to guess. I can only base my estimate on the features theyâve let us test so far.
A month or two ago I was more pessimistic about the timeline, but having tested the latest version of Logseq DB I am really impressed with the progress they are making.
This 
I assume youâre testing de DB version on the browser, right?
I am a paying user of the MD version. When the DB version is rolled out, will I be automatically transferred? And will the existing plug-ins still work? @Ramses
2 Likes
@pavl74 please note that Logseq doesnât have a subscription service. You being a âpaying userâ means that you donate.
Because we use an Open Collective to receive donations, thereâs no payment info we can transfer. Once Logseq Pro launches, you will receive an email with instructions on how to start a subscription with Logseq (for those afraid Logseq will become a paid app; this is only for the optional Logseq Pro service that will include sync, real-time collaboration, and publishing). If you donate now, you will get a permanent discount.
The release of Logseq DB is separate from sync for Logseq DB, by the way. Sync will be ready at a later point.
You can check the answer for yourself at https://test.logseq.com. Some plugins already work, some others need to be adapted by their developer.
If you have more questions about plugins in the DB version, please first search the forum for existing topics and otherwise create a separate topic.
I did not know this! Does it have to be a recurrent donation� Or is there somewhere I can read more about this?
Thank you!
2 Likes
There hasnât been any communication about this (apart from what Iâve shared here and there on the forum and our Discord). This is based on discussions internally and what I think will 99% likely happen.
4 Likes
Development seems quite unfocused at the moment from looking at the changelog. Thereâs changes in the query builder, iOS and whiteboard in the latest release, why is this being prioritised rather than outstanding importer todos?
This is stuff that could very easily be worked on post-DB release, which many of us here have been patiently waiting on for years whilst the performance of the MD/Org version continues to frustrate.
I thought that the importer todos would be the highest focus so that the app can progress to a wider desktop alpha, but it looks like the focus is instead on polishing literally anything else.
7 Likes
agreed, lisp and org syntax looks exciting, maybe even a possibility for literate programing.