Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

VisualJJ – Jujutsu in Visual Studio Code

visualjj.com

Post reply on HN
Print view View original

41–50 of 90 posts

Re: VisualJJ – Jujutsu in Visual Studio Code

#41

Post by Zambyte »

knallfrosch wrote: post #38
j1elo wrote: post #37

Earlier quoted context omitted.

I find it a bit ridiculous to see that people or whole teams don't want to use JJ (or any tool, for that matter) because in essence they hired a "support intern" (read: AI assistant) who doesn't know or want to use it.

Why would I learn the abstraction of JJ on top of git when I've got a butler who's happy to deal with git directly? You're right in principle, but it just seems JJ is a solution in search of a problem.

How does your AI agent deal with large merge conflict resolution?

Re: VisualJJ – Jujutsu in Visual Studio Code

#42

Post by aniforprez »

sunshowers wrote: post #39
hippo22 wrote: post #14

Earlier quoted context omitted.

I agree it will hold back new technologies, but, at the same time, I'm not sure what the value add of new technologies will be going forward. Often, as is the case with git vs. jj, the value add of a new technology is mostly ergonomic. As AI becomes more ingrained in the development flow, engineers won't engage with the underlying tech directly, and so ergonomic benefits will be diminished. New technologies that emer…

Ah yes, the inevitable future where the only way we'll know to interact with the machine is through persuading a capricious LLM. We'll spend our days reciting litanies to the machine spirits like in 40k.

Praise and glory be to the Agentic gods. Accept this markdown file and bless this wretched body of flesh and bone with the light of working code. Long live the OpenssAIah

Re: VisualJJ – Jujutsu in Visual Studio Code

#43

Post by codethief »

> Stay in your editor while GitHub does the rest. VisualJJ tracks pull-request status on the change tree and lets you create PRs in a couple of clicks, so moving changes from “draft” to “merged on GitHub” feels like one smooth flow.

Does it support stacking PRs?

EDIT: I should have looked more closely, looks like it does, though only in the Pro version: https://www.visualjj.com/docs/stacking

Re: VisualJJ – Jujutsu in Visual Studio Code

#45

Post by avarun »

Zambyte wrote: post #41
knallfrosch wrote: post #38

Earlier quoted context omitted.

Why would I learn the abstraction of JJ on top of git when I've got a butler who's happy to deal with git directly? You're right in principle, but it just seems JJ is a solution in search of a problem.

How does your AI agent deal with large merge conflict resolution?

It just reads through the merge conflict and intelligently resolves it. This is not a problem.

Re: VisualJJ – Jujutsu in Visual Studio Code

#46

Post by SatvikBeri »

stouset wrote: post #33
Yeroc wrote: post #12

Earlier quoted context omitted.

Seeing similar comments across different articles and technologies and it makes me wonder how much AI is going to hold back the adoption of new technologies going forward.

Claude Code has zero issue using jj, for what it’s worth.

I noticed it get a lot better with the 4.5 models specifically. Before then, I would have to tell Claude "do a web search for the docs for jj, then do XYZ." Now I just tell it to "do XYZ using jj"

Re: VisualJJ – Jujutsu in Visual Studio Code

#47

Post by aabhay »

KingMob wrote: post #40
Okkef wrote: post #36

Earlier quoted context omitted.

It usually works, but sometimes it'll try to use git instead of jj at random and needs a reminder. As JJ is not completely stable it tries some old commandline versions as well. This improved after I put in some lines in my agents file, but still it's much better at complex changes with git than jj.

If it helps, this was all I needed in my CLAUDE.md to make it use jj perfectly: # Version Control - IMPORTANT: YOU MUST assume we use Jujutsu ("jj") for version control. Check by running `jj root` (or look for a `.jj/` directory) to confirm. - If I say "commit", "branch", "squash", etc., assume jj equivalents first. - You can ignore any `git add` command, since jj always auto-adds. - Use `jj` commands instead of `git…

You can set jj to auto update stale workspaces btw

Re: VisualJJ – Jujutsu in Visual Studio Code

#48

Post by meling »

Great to see this. I played around with jj about two months ago and really enjoyed using it on the command line, but I found it difficult to understand the interaction with git and GitHub and decided to put it off until I had more time. (I don’t recall the specific issues I had…) Maybe this extension can remove some of that friction.

Re: VisualJJ – Jujutsu in Visual Studio Code

#50

Post by tuwtuwtuwtuw »

steveklabnik wrote: post #26
AbuAssar wrote: post #8

Earlier quoted context omitted.

it is worth noting that Jujutsu uses Git’s storage, networking, and ecosystem.

It uses it when you use the git backend, but not when you don’t. Right now, the only other backend is at Google, so it’s not practical for most people. But it’s not an inherent part of jj, and that’s really important, actually.

For anyone that does not work at Google, it sounds like an implementation detail that does not matter.
Post reply on HN