2 ms·
Git - jj[1] uses gitoxide for its git interop/backend (git being the backend of jj you're expected to use), both Apache/MIT; it functioned so cleanly I assumed
by dzaima 1y ago
Git - jj[1] uses gitoxide for its git interop/backend (git being the backend of jj you're expected to use), both Apache/MIT; it functioned so cleanly I assumed it was invoking git directly, but apparently it's all custom!
For new things I'd guess PostgreSQL vs MySQL is probably on the same order as llvm vs gcc; probably with PostgreSQL being better off than llvm even.
[1]: https://github.com/jj-vcs/jj/ https://github.com/jj-vcs/jj/ (started by a Googler as a hobby project, now their full-time job at Google, so kinda fits into the "big orgs will replace things with permissive-licensed versions" narrative)
- steveklabnik 1y agojj does shell out to git for network operations these days, but the majority of it is gitoxide, that's right.
- dzaima 1y agoAh, that appears true. I just tested some commit creation & state inspection commands, didn't bother with network stuff.
- steveklabnik 1y agoIt’s a recent change, there were just too many folks who had network requirements that it couldn’t do, so it’s easier to just piggyback on top of git, which supports all that stuff.