Q: Is it ready to replace Dataview?

[LePenseur13]

Is this plugin ready to replace Dataview as a daily used plugin?
If not, then when approximately will it be, or what is missing for it to be ready?

I know this is not a normal issue. I am just really curious, because I use Dataview so much and this sounds amazing: faster and some killer features.

When it is ready I would also use it to give coding agents more structured access to my vault.

[roman-balzer]

It's ready, i'm using it for most stuff. Tho for simple stuff I still use Dataview (but this is rather rare)

I just think it's harder for most since A. it's not that well documented and B. it's more developer focused. (My opinion)

[FrBosquet]

I don't see it as a direct replacement, its more dev focus as @roman-balzer said and you need to be somehow familiar with Preact and JS to write good components.

As for I would also use it to give coding agents more structured access to my vault I don't think this would serve you: Datacore renders html inside obsidian that you can view when you open the note, but is not persisting your tables or documents anywhere. If you point your agent to those notes, they are going to see the datacore code, not the result of your queries

[jwhonce]

I would look at #100 this is the biggest gap for me. I use dataview and datacore, but lean on datacore for building MOC pages through queries. I really like the control on rendering data and performance improvements.

[LePenseur13]

thank you guys for the quick response.
Great to know that you use it to replace most of your dataview usage.

[LePenseur13]

@FrBosquet I was thinking since the index and the metadata is much faster than dataview, I would write something simple on top of it like a CLI that enables a coding agent to access that data.
I'm especially interested in tasks, metadata, quickly accessible, fast index live updates.

Currently I'm using https://github.com/tobi/qmd. But a fast datacore index for other things would be a great addition.

[LePenseur13]

@jwhonce The pull requests that you mentioned is it mostly about how tasks are displayed or is it also about the index over those tasks? As I said before, that will be crucial for me.