So, the browsers have to provide some means for choosing the desired translation engine (add-on API maybe?) and this is a standard API which all of the providers should implement.
This part was not obvious. In a lot of cases geodata is mostly stable and reads/searches dominate over appends. And that’s why we keep this in DB (usually postgis, yes).
So DuckDB is optimised for very different use case and it is not always obvious when it’s mentioned
Well, jj is actually very nice in this regard, because:
1. it works on top of git — you keep using all the same infrastructure (GitHub, etc.)
2. in your local repositories you still have access to git-tools, as jj maintains git and its own states in sync.
After all of these months with jj I still find myself using GitUp when I need to review a long chain of commits or do some quick repo-archeology.
And, from time to time, I even use Idea's merge tools because their "magic wand" saves a lot of time.