←back to thread

I see a future in jj

(steveklabnik.com)
325 points steveklabnik | 2 comments | 22 Oct 25 17:21 UTC | HN request time: 0.401s | source
Show context
j2kun ◴[22 Oct 25 20:58 UTC] No.45675064[source]▶
> I also don’t mean to imply that everyone at Google is using jj, but the contingent feels significant to me, given how hard it is to introduce a new VCS inside a company of that size.

I don't mean to imply that Google is fickle, but anything besides Google's perforce fork is deprecated every few years. We used to have a proper git wrapper, then mercurial+extensions, now jj is supposed to replace the mercurial thing, all in 7-ish years?

replies(4): >>45675071 #>>45677002 #>>45677749 #>>45679002 #
joshuamorton ◴[23 Oct 25 00:53 UTC] No.45677002[source]▶
I don't think this is quite right.

The git wrapper was never fully supported and had some rough edges (I think it was only ever a 20% project, and also its, like, really old). And the customized mercurial has been around for more than 7 years, I think close to a decade (the client I'm using right now is turning 7, and it wasn't my first one).

replies(2): >>45677121 #>>45678596 #
1. diegs ◴[23 Oct 25 05:55 UTC] No.45678596[source]▶
I used git5 from when I started in 2011 to when I left in 2017.

I'm going back starting on monday, so I'm curious to try out jj.

In the past 10 years it's all been github and gitlab, and their code review tools are so painful, specifically w.r.t. tracking discussions across revisions. I never felt excited to try out jj because I was afraid it would that situation even worse.

replies(1): >>45678776 #
2. wutbrodo ◴[23 Oct 25 06:22 UTC] No.45678776[source]▶
It was deprecated in 2015 iirc