←back to thread

I see a future in jj

(steveklabnik.com)
291 points steveklabnik | 10 comments | 22 Oct 25 17:21 UTC | HN request time: 0.456s | source | bottom
Show context
weinzierl ◴[22 Oct 25 20:14 UTC] No.45674580[source]▶
I think the real news is that some people have started to build what might become something like a "jjhub".

https://ersc.io/

replies(7): >>45674802 #>>45675236 #>>45675335 #>>45675688 #>>45677818 #>>45678591 #>>45678833 #
1. steveklabnik ◴[22 Oct 25 20:34 UTC] No.45674802[source]▶
I think 'jjhub' is a decent immediate first approximation, and is often how I've started out talking about it with people. At the same time, we have to offer real value here, as you can already use jj with github (and I have for a long time now), so there's more to it than that. But yes :)
replies(3): >>45675242 #>>45676675 #>>45678269 #
2. davidkunz ◴[22 Oct 25 21:16 UTC] No.45675242[source]▶
What I would love:

- Everything locally stored in the repo: PRs, comments, issues, discussions, boards, ... - CLI first - Offline first (+ syncing) - A website for hosting/presentation

replies(2): >>45675308 #>>45675504 #
3. steveklabnik ◴[22 Oct 25 21:22 UTC] No.45675308[source]▶
Noted :) In another comment I linked to beads, which is a cool project to keep your issue tracker in your repo, but that's just a personal thing, no comment on what the company plans to do (or not) in this area.
replies(1): >>45677860 #
4. ElectricalUnion ◴[22 Oct 25 21:40 UTC] No.45675504[source]▶
So you want Fossil?
replies(2): >>45676492 #>>45677093 #
5. arccy ◴[22 Oct 25 23:32 UTC] No.45676492{3}[source]▶
except fossil decided to never allow changing history, vs jj which makes history rewriting so much easier
6. gravypod ◴[23 Oct 25 00:02 UTC] No.45676675[source]▶
I would love having some first class support for monorepos at bigger organizations (ex: silos, vfs, etc).
replies(1): >>45676783 #
7. steveklabnik ◴[23 Oct 25 00:17 UTC] No.45676783[source]▶
No promises but noted for sure…
8. anotherevan ◴[23 Oct 25 01:10 UTC] No.45677093{3}[source]▶
When I tried Fossil it had things weirdly separated.

I was expecting when I make a commit, I would have the facility to specify what issues it addressed and it would close them for me automatically. It seemed there is so much opportunity there to "close the loop" when the issue tracker, etc and integrated in your VCS, but it wasn't taken.

9. antonchekhov ◴[23 Oct 25 03:26 UTC] No.45677860{3}[source]▶
I use command-line tooling much more than IDEs (e.g. VS Code), so the `gh` command-line tool (https://cli.github.com) for doing most of the usual hub-oriented workflow (PR authoring, viewing issues, status updates, etc) really helps a lot - I don't have to constantly <cmd>+<tab> to my browser, and point-click-point-click through web pages so much. It would be fantastic if ersc or any other jj-centered code-sharing hub had similar tooling early on.
10. saulrh ◴[23 Oct 25 04:53 UTC] No.45678269[source]▶
If you're starting over with a new backing store using jj's pluggable backends, can you give us a native lazily-materialized store for megarepos? It's a tragedy that the open-source world has no answer to piper.