But jj supports git as a backend, so not clear what fracturing you mean, do people using magit front-end fracture?
This allows the people who want the 15% gain to have it, while not forcing anyone to do a costly migration.
Having distinct local working copies of same repo per git branch still works great, not stash needed, no conflicts or pain with local wip and drafts changes overwritten by pull. No blocker for switching branches. No reset hard/soft whatever. And makes files comparisons easier and makes my git workflows easier.
I still feel vcs could be simpler and solved problem if more engineers care about the topic of vcs and generally speaking about the ux of their main tools instead of creating new TUI and plugins to workaround broken ones.
I was a git power user. I became comfortable enough with jj to replace git entirely in one day.
If Linus had this mentality we’d all still be using Subversion.
Every single engineer has to start over in their mastery experience by learning all the new quirks and issues, and all the tools, libraries, pipelines need to be rewritten.
IMO better to support the dominant tooling than invest in fracturing one of the few areas where engineers can agree on something for once (to everyone's benefit).