OTOH you get version history, with commit messages if you care to write them. And the full power of git to explore the history. You can edit the same file on two (offline) devices, then resolve the inevitable merge conflict.

"Automatic bidirectional sync between all devices" scares me. How does it deal with merge conflicts? How am I sure I'll be able to revert to a previous version? Can I see the full history of a file? I don't know, perhaps it'd be ok. I certainly wouldn't learn git just for note taking! But, I know how to use my hammer, so everything look like a nail...

You can automate commits and push on save. I had a similar setup for vimwiki before migrating to a web-based wiki system (dokuwiki).

I thought it would be a problem as well but it turns out I absolutely never edit my notes on two machines at once. The commit/push/pull is done via a simple bash script that I'm running as a build command inside VS Code.

I like it as I consciously enjoy sort of checking in.

I also store in a onedrive folder for automatic sync and backup in case I have a crash before I do a git commit.

Is that really useful? How often do you need to revert a commit?