3 Dominant Themes from the Discussion
1. Excitement about the JJ workflow (megamerges, absorb, parallel streams)
- “If this works like I think it does, it might be the missing piece I've been waiting for, for actually trying jj. Thanks!” – grim_io
- “love to see it, been looking forward to this.” – schpet
- “this is great stuff. I've been ad‑hoc building a version of this workflow, and it is quite fantastic.” – dbt00 - “Awesome! Tbh other than GitButler idk where I'd even start if I had to recreate this with vanilla Git.” – icorbrey
Bottom line: Users see JJ’s megamerge and absorb features as a game‑changer for handling complex, parallel work.
2. Strong community support & complementary tooling
- “I also can't recommend the Discord[1] enough. The community is very helpful and welcoming.” – nvahalik
- “visualjj, it’s fantastic.” – altano
- “jj is infinitely more user‑friendly, and as the tool matures, it isn’t far fetched to think a new generation of programmers could go straight to jj without knowing their way around git first.” – ksymph
The community (Discord, jjui UI, visualizers) is highlighted as a key enabler for newcomers.
3. Practical concerns around conflict resolution and coordination
- “When using megamerger workflow, most of the problems come from coordinating with other colleagues.” – rixtox
- “I found octopus megamerge hard to collaborate … eventually I settled on a tree‑like megamerge … you have to be very careful to decide the order when you (and your colleagues) are going to land the branches.” – rixtox
- “I do not understand the appeal of the workflow of working on separate things in parallel, then splitting it off into branches/commits… I might accidentally split it off in a way that makes it uncompilable.” – b1temy
Several commenters stress that while the workflow is powerful, it introduces coordination complexity, especially in team settings.