Logseq talks about the DB version
Вставка
- Опубліковано 30 тра 2024
- So yesterday we got a surprise announcement on the DB version, what the plans are and why things are taking so long. Decided it might be a good idea to go through it and give some thoughts.
Original post here - discuss.logseq.com/t/why-the-...
==== 🧾 Table of Contents 🧾 ====
00:00 Intro
00:25 tienson's introduction
01:15 FAQ
03:20 Context
17:21 Challenge
23:35 Projects status
25:35 FAQ
30:57 Future plan
33:45 Replies
36:33 Outro
Thanks for the shoutout ❤ queries are a complex topic, as you said as well, the bar to entry is extremely high.
I love queries but really want it in the hands of everyone. Simple queries was a huge step forward but only a first step in my eyes
Very excited. Can‘t wait for this.
For those wondering org support is not planned for the database version at this time
Crucial information for those using org mode. It's a bit of a shame though if DB becomes the central source it might be nice if we could get two-way sync to different formats with plugins. Org mode, Ascii doc, yaml.
Thnx
Will Logseq sync with DEVONthink? Right now DT syncs with Obsidian
I doubt it will unless DEVONthink can read the two-way markdown sync.
Knowing the current and planned featureset of Logseq, I think no sane developer would choose markdown as a backend. It's amazing that it works as well as it does, but it's like entering a Formula 1 race on a bicycle and thinking "if I train my legs hard enough I can win this"
Its shame theres no pkm tool based on asciidoc, and instead multiple flavours of markdown are used
True Story, in Germany we have an extreme bad internet connection :(
With such a long list of why the markdown files are so terrible it makes me wonder why they even did it like this.
Personally, a database will take away the reason why I started using this.
Logseq started as a clojure implementation of org mode, so text files on the system was at its core. Then markdown was added because a lot of people prefer that. Pure numbers thing as far as I could tell. I don't think markdown is terrible, but it's a bad fit for where Logseq is going as far as main storage. But I wouldn't make it out as bad as it is, don't forget there's an in memory system that's already used (what re-index) does and that's also some kind of db between de md files on disk and what you see in the app.
whenyouskipsilencesofyouraudioitlistenskindofhowiamtyping.somewhatexhoustingthanksthoughappreciateyourvideos
Feedback noted, should be better in the next video. Thanks for the feedback, really helps!
@@toolsontech counterpoint its a lot nicer than the slow interrupted pacing with silences that some people have. With excessive pausing I just skip ahead to get to the words.
@@mystixa I'm trying to find the right balance with my editor, super happy with the counterpoint and taking both in account I'll do a double take on the future videos at single speed to see if the "flow" is right.