←back to thread

I see a future in jj

(steveklabnik.com)
291 points steveklabnik | 4 comments | | HN request time: 0.624s | source
1. baq ◴[] No.45674018[source]
I’m just sad pijul doesn’t get the same attention or love from the community. It desperately needs an ability to colocate with git.
replies(2): >>45674403 #>>45676045 #
2. mirashii ◴[] No.45674403[source]
I think that the ability to collocate with fit is really the thing that makes even evaluating the use of jj feasible in many organizations. To consider pijul, it requires throwing away all of your forge setup, configuration, permissions, backup, disaster recovery, as well as updating every CI pipeline.

In a very real way, git won, and the inertia behind git is higher than it was for any VCS tool before it, and so just being better isn’t going to be enough, you’ll also need to interoperat.

3. dagenix ◴[] No.45676045[source]
I strongly suspect that its not feasible to colocate pijul and git. git and jj are based on snapshots, while pijul is based on patches. They have very different models.
replies(1): >>45678741 #
4. baq ◴[] No.45678741[source]
As long as some repository state in either system can map onto a checkout in the other system it should be possible at least in some capacity. I’d like to try out pijul at work, but I’d need an analog of jj git fetch and jj git push. Whatever happens in between doesn’t really matter too much unless it’s tedious manual bookkeeping to maintain history mapping.