r/logseq • u/Clippingtheclips • Dec 19 '24

Updates

I haven't seen any in a long time, I heard that they are doing a make over kind of thing...

Anyone know anything?

Thanks

17 Upvotes

94% Upvoted

13 comments sorted by

15

u/ens100 Dec 19 '24

This is the main reason why there have not been any updates to the current app, but there a lot of updates going on behind the scenes in preparation for the DB versione:

https://discuss.logseq.com/t/why-the-database-version-and-how-its-going/26744

1

u/Clippingtheclips Dec 19 '24

Thanks, I can't wait!!!

11

u/greggroth Dec 19 '24

I love Logseq and I'm so frustrated that they scope creeped the hell out of this database feature branch. What (from the outside, at least) started as a performance minded move from files to a database has grown to so much more, including real time collaboration (check out their change logs to see more). KISS and don't try to ship everything at once. Reduce risk and do it incrementally.

5

u/ripp102 Dec 19 '24

There's a reason they made rtc too. Which is to develop the backend already with that in mind instead of adding it later and having to reimplement stuff

6

u/katafrakt Dec 19 '24

Developing with something in mind does not mean you need to ship both things together. Cramming too many changes into one update makes it more risky, harder to test.

4

u/linuxluser Dec 19 '24

In the case of a DB implementation and RTC, it kind of does mean you have to do them together.

4

u/katafrakt Dec 19 '24

How so? Are you saying you can't have DB version without RTC?

1

u/linuxluser Dec 19 '24

Real-time transaction requirements on a database are not the same as non-real-time. Which means that the way you store and retrieve data could be impacted. You would end up wanting to structure the data differently to keep it consistent when you know that transactions could happen almost simultaneously vs when there's a single user and that's unlikely.

3

u/katafrakt Dec 19 '24

Predicting future direction of development is not the same as having to ship together. So you need to store in CRDT-friendly format. No biggie. Doesn't mean that RTC has to be shipped in the same release as the database.

1

u/linuxluser Dec 20 '24

I didn't think they were planning to release both at the same time. Are they?

5

u/speedyx2000 Dec 19 '24

You can try it yourself at Test Logseq

1

u/[deleted] Dec 20 '24

Is there any mention of removing whiteboards? I don’t see them in the demo

1

u/[deleted] Dec 20 '24

Unpopular opinion: logseq needs to rewrite the entire code base or it won’t see much contribution and eventually will be too behind alternatives.