GitKraken Client Is Migrating from Libgit2 to the Git Executable

I've built a UI on top of libgit2 and I wish that this blog post expanded on which new features are missing (sparse checkout?).

To quote: "The migration to Git Executable will allow us to resolve long-standing issues with GitKraken Client, such as poor LFS performance, SSH configuration support and many other features/performance improvements."

I agree on LFS performance on Windows. SSH config support is a pain due to libssh2 but openssh support is on the way (https://github.com/libgit2/libgit2/pull/6617).

There are many cons to using the Git executable itself (parsing output, error reporting, version handling). Seems to me that there's more to this?

What are/were Axosofts libgit2 contribution numbers like? If Gitkraken is their bread and butter, why the hell aren't they sponsoring the developement with money and man power on the library they entrust? This post reads like an exploitive expose, ie. we profit on open source.

Or my condescending take is that Copilot/ChatGPT struggles with API generative code and it is far easier for the prompt "engineers" to generate a system call from the git man page.

I wish they would have put this energy into adopting web workers. It really sucks that you can't switch repository tabs while waiting for git operations to finish.