iOS makes it painful to use third-party sync protocols and servers, like syncthing can't run in the background, a git sync service can't run in the background, only iCloud gets to run in the background.... and whatever sync protocol the app itself has blessed so it can run immediately on opening the app.
As such, on iOS the native sync is the only one that works cleanly and seamlessly, and so you're incentivized to pay for it.
There was a little while, when dropbox was big, where it seemed like the future of computing would be "your data is in the cloud, and every app you use can share that data, and those two things are independent integrated through some common filesystem layer".
And then it ended up that no, your data's in a cloud-per-service, where your emails live in googles cloud, your documents in microsoft 365's cloud, your images in "adobe creative cloud"'s cloud, your photos in Apple's cloud, your passwords in 1Password's cloud, and your knowledgebase in Obsidian's cloud.
The dream of the filesystem API being able to expand to clouds, of being able to choose dropbox or google or apple as the owner of your data, and other applications seamlessly integrating with any of them, it died with apple making it impossible to offer any sort of generic filesystem API or even background sync.
And so, that's why you'd use obsidian sync over git, because you're cursed with using a phone.
Unless you're saying "why not pay for obsidian sync, but then sync it into a git repo in CI and commit there to see the diffs", not "why not use git as the underlying sync protocol", in which case ignore everything I wrote, you totally could do that.
Which gates "sync" behind an expensive "premium" paywall.
It feels criminal to charge that much for the sync feature when it also can't possibly work, iOS actively does not want apps to run in the background, and does not offer a viable method for this libgit wrapper to execute libgit on, for example, a filesystem inotify event or write or whatever.
What do you know, people are observing it doesn't really work.
> Apple's iOS has a pluggable Files system.
Okay, excellent, maybe you can tell me how to do this.
I have opened the builtin iOS notes app. It by default can sync notes with iCloud. I would like to have it store my notes in Git or Dropbox or anything else, and be able to also edit them on another machine and have the changes sync.
I won't hold my breath on how to do this because like clearly things are not pluggable, the builtin iOS apps don't work with anything but iCloud and the filesystem is obviously not pluggable or generic.
If you have automation that dumps things int your vault, that you built with their new CLI (which lets you create/tag docs etc. without running the full electron app), I guess this lets you sync those changes and propagate them to all of your obsidian sync clients also without having to open aforementioned full electron app.
Only in 2nd-brain mythology, which holds that you'll discover connections between your notes that you didn't realize was there. I think it started as eye candy to confuse prospective users considering Roam Notes. They later did something similar with their "Canvas" feature. So, these are features you get with their lack of coherent vision, rather than basic usability and a safe plugin ecosystem, neither of which Obsidian plans to deliver..
Let me provide a counter argument: with the graph you can browse your notes visually in 2D, instead of just the usual list. You can just take notes as usual, easily add #tags and [[links]] in them, and then when you go to graph view you can see connections between those links and you can color code or filter tags. You get a global graph view of all your vault, and local view of any note. Links and tags are literally the core Obsidian features and the graph view sits on top of that. For me that is a coherent vision and utility.
Sorry, the lack of vision I referred to related to Obsidian's leadership -- unserious D&D kids largely unconcerned with usability, performing security theatrics with sync e2ee while their users data is regularly at risk of mass exfiltration via their insanely dangerous community plugin ecosystem.
The on-screen appearance of the feature you're referring to may be visual and coherent, I'm just pointing out that users frequently cite theoretical or anticipated benefits of this feature, not real ones.
As such, on iOS the native sync is the only one that works cleanly and seamlessly, and so you're incentivized to pay for it.
There was a little while, when dropbox was big, where it seemed like the future of computing would be "your data is in the cloud, and every app you use can share that data, and those two things are independent integrated through some common filesystem layer".
And then it ended up that no, your data's in a cloud-per-service, where your emails live in googles cloud, your documents in microsoft 365's cloud, your images in "adobe creative cloud"'s cloud, your photos in Apple's cloud, your passwords in 1Password's cloud, and your knowledgebase in Obsidian's cloud.
The dream of the filesystem API being able to expand to clouds, of being able to choose dropbox or google or apple as the owner of your data, and other applications seamlessly integrating with any of them, it died with apple making it impossible to offer any sort of generic filesystem API or even background sync.
And so, that's why you'd use obsidian sync over git, because you're cursed with using a phone.
Unless you're saying "why not pay for obsidian sync, but then sync it into a git repo in CI and commit there to see the diffs", not "why not use git as the underlying sync protocol", in which case ignore everything I wrote, you totally could do that.