18 ms·

It's certainly a solid improvement in the space of VCS UI, but beware that jj has some current limitations which might prohibit switching, especially for the gi

It's certainly a solid improvement in the space of VCS UI, but beware that jj has some current limitations which might prohibit switching, especially for the git power users. Lack of gitattributes support precludes git-crypt and git-lfs usage or anything that needs filters; line ending settings will get ignored, making Windows interop a little less smooth; etc. Also note that auxillary tooling, such as git-annex and git-bug, becomes second class, i.e. no oplog integration and they might mess up your log with internal-use commits and heads.

steveklabnik 1y ago
> line ending settings will get ignored, making Windows interop a little less smooth; etc. This one got fixed just a few days ago! https://github.com/jj-vcs/jj/pull/6728 https://github.com/jj-vcs/jj/pull/6728
stouset 1y ago
These are all really excellent points, and well worth calling out.
Ayesh 1y ago
I use gitattributes quite a lot (lfs, various diff engines, and export-ignore). Thanks for the heads-up, jj looked very interesting but I'm not going to give up gitattrivutes.
- dilap 1y ago
  They are slowly working on it: https://github.com/jj-vcs/jj/issues/53 https://github.com/jj-vcs/jj/issues/53 (I am interested because I want to try, but need git-lfs, which needs gitattributes.)
IshKebab 1y ago
> line ending settings will get ignored Arguably a good thing - git's autocrlf setting causes way more issues than it solves. I highly recommend setting it to "input" (basically bans CRLF).
stavros 1y ago
Oh thanks for the heads up! I use jj but it would be a disaster if I committed something using it and git-crypt didn't work, and the secrets were all plaintext.
BeetleB 1y ago
> line ending settings will get ignored, making Windows interop a little less smooth; I hit this - I develop in Windows. I still prefer jj and won't go back to pure git :-)

steveklabnik 1y ago

> line ending settings will get ignored, making Windows interop a little less smooth; etc. This one got fixed just a few days ago! https://github.com/jj-vcs/jj/pull/6728 https://github.com/jj-vcs/jj/pull/6728

stouset 1y ago

These are all really excellent points, and well worth calling out.

Ayesh 1y ago

I use gitattributes quite a lot (lfs, various diff engines, and export-ignore). Thanks for the heads-up, jj looked very interesting but I'm not going to give up gitattrivutes.

dilap 1y ago
They are slowly working on it: https://github.com/jj-vcs/jj/issues/53 https://github.com/jj-vcs/jj/issues/53 (I am interested because I want to try, but need git-lfs, which needs gitattributes.)

IshKebab 1y ago

> line ending settings will get ignored Arguably a good thing - git's autocrlf setting causes way more issues than it solves. I highly recommend setting it to "input" (basically bans CRLF).

stavros 1y ago

Oh thanks for the heads up! I use jj but it would be a disaster if I committed something using it and git-crypt didn't work, and the secrets were all plaintext.

BeetleB 1y ago

> line ending settings will get ignored, making Windows interop a little less smooth; I hit this - I develop in Windows. I still prefer jj and won't go back to pure git :-)