Unless there's another set of reasons you're worried about it?
If my brain worked like a database, I'd already be using one of the dozens of products that depended on a database structure. I don't doubt that this will be more mainstream because of the decision, but it will ruin what made the product useful for me.
Most of the existing workflows remain the same and the DB version opens up many more workflows. Would recommend trying it out if you haven't already with https://test.logseq.com/ and https://github.com/logseq/docs/blob/feat/db/db-version.md. If you have tried it out, please give us feedback :)
For example, I like just popping "TODO" on the front of a line, but the database version adds a bunch of stuff I don't want. I don't want to have a drop-down list pop up with distracting icons that don't even have a cohesive color scheme. I don't want to have to move my cursor down a list. I just want to click where it says TODO and have it change to DOING and then change back when I click it again, and then change to DONE when I click the box. I don't want tags on the ends of my lines. I like having the status right at the front, not singled out as just one more property, but just there, where I would put them if I were writing things down without software. I don't want to have to set properties, and I don't even use tags as a separate thing to be attached to my blocks, certainly not right-aligned.
What made Logseq elegant in its simplicity is absolutely ruined for me with the database version. It is the most concerted effort I've ever seen to destroy the best parts of the product to make it into something entirely different.
And it's fine that you're going to do it anyway. I'm just disappointed I'll be stuck sitting on a version that never moves forward, because there was SO much room for improvement, especially on mobile, which now won't ever happen to the product I actually love.
Tasks can be created with `/todo` and additional ways - https://github.com/logseq/docs/blob/feat/db/db-version.md#cr...
> I don't want to have a drop-down list pop up with distracting icons
The Status property is customizable - https://github.com/logseq/docs/blob/feat/db/db-version.md#cu.... If you don't like the icons, you can delete them from a property's Available Choices - https://github.com/logseq/docs/blob/feat/db/db-version.md#pr...
> I don't want tags on the ends of my lines
Then press `Cmd-Enter` as the ui tells you todo and as documented in https://github.com/logseq/docs/blob/feat/db/db-version.md#cr.... Tags entered that way display as before
> I like having the status right at the front, not singled out as just one more property
It is in the front and the position of a property is configurable ¯\_(ツ)_/¯
That's why I rejected using Notion. Using it requires forcing my mind to operate inside someone else's system.
Logseq finally felt like someone whose brain works like mine made software for people like me.
And now it's being systematically dismantled for the sake of the hordes of people who already have other tools serving them just fine.
Like I said, I get that it's not my call and people are going to do it anyway. I just hate it more than I've ever hated any software change I can remember.
Every time the Johnny.Decimal system resurfaces on HN, though, I'll admit to spending a couple weeks revisiting the task of finally systematizing the decades of old files stored on my hard drive, until I remember that I haven't looked for any of them in many years, never mind opened them, so it's probably not worth any effort after all.