Live data from Hacker News

Jujutsu at Google [video]

youtube.com

101–110 of 212 posts

Re: Jujutsu at Google [video]

#101

Earlier quoted context omitted.

one thing which causes problem with git for me is collaborative work without using "git server". This usually comes up at homelab situation with no access a "git server" or ssh server. One thing with jj is i can use existing sharing mechanism like dropbox, google drive or if nothing else just copying jj folder (granted all of those are bad idea w.r.t vcs but still).

I don’t understand this critique. You can copy a .git folder around just fine. You can expose a “server” by giving friends ssh keys that can only access the git stuff. In fact for a long time that’s how git “was done” at various corps.

> You can copy a .git folder around just fine.

You can do this, but due to file locking, you can corrupt the state if it's shared. jj is specifically designed so that it won't corrupt the repo in this way: https://jj-vcs.github.io/jj/latest/technical/concurrency/

Re: Jujutsu at Google [video]

#102
post #84

Earlier quoted context omitted.

A technical presentation is a still a presentation, as opposed to a reference document. If you want to give someone a block of technical information, you do so in a reference document. You talk in front of a room full of people in order to convince them that this matters enough to bother.

Sure, but I don’t think this is relevant to the comment thread we’re in, which started off by sharing generic advice that mostly applies to TED-style motivational talks or “keynotes” at large conferences etc.

I definitely thought we were downstream of pinkmuffinere's critiques about not establishing a reason to be excited about the material. oops.

Re: Jujutsu at Google [video]

#103
post #46

jj is so good, finally a tool to replace Git. SVN -> Git -> jj

No LFS, submodules, hooks, or new tags means jj has some ways to go before it is a viable replacement for many organizations https://jj-vcs.github.io/jj/latest/git-compatibility/

LFS sorta works and submodules are just managed by git, and you can create tags with the git CLI just fine.

Hooks are a bigger change, though, for sure.

Re: Jujutsu at Google [video]

#105
post #18

I've worked in huge repos with hundreds of developers pushing code every day, dozens of MRs open per day, and all I always needed was a very limited set of what git is capable of (git commit, git co, git st, git merge/rebase, git log). To find bugs, I use "bisect but visually" (I usually use jetbrains IDEs, so I just go to the git history, and do binary search in the commits, displaying all the files that were affect…

I have never understood the claim that git is hard. the docs are good and there are plenty of examples online. feels the same when people say, "jq is hard i use python instead" like ok

Even though I never found git hard, I find jj better.

Re: Jujutsu at Google [video]

#106

Earlier quoted context omitted.

From time to time, I end up in a state which I don't know how to recover from, and it's very frustrating to have to take an hour or two from my real work in order to try to figure out how to get out of that state. https://roadrunnertwice.dreamwidth.org/596185.html

The reflog is the failsafe. It is the tool that fixes all the scary states, as it keeps a journal of the states of each ref in the repo (like branch heads). You can see where you were and hard reset back, no matter what state you are in.

If you like the reflog, you'll love jj's oplog: it's like the reflog, but for all repository state changes.

Re: Jujutsu at Google [video]

#107
post #19
post #6

>Jujutsu, aka JJ, is an open-source, Git-compatible VCS

Thanks for that context. Why would I want to use it instead of git?

Here's what I wrote about it eight days ago: https://news.ycombinator.com/item?id=45673808

Lots of other opinions in that thread too.

Re: Jujutsu at Google [video]

#108
post #97

Earlier quoted context omitted.

I think what people usually mean is "scary" or "it's easy to mess up". Git is very easy to use until you mess up, then it can become complicated, and certain actions may have devastating consequences. Two examples from recent memory: Someone merged the develop branch into their branch, then changed their mind and reverted the merge commit specifically (i.e. reversing all the incoming changes), then somehow merged all…

I mean. How can it be scary when you have git reflog.

The reflog doesn't capture everything. jj's oplog does.

An example of something that the reflog isn't going to capture is a git reset --hard losing your unstaged changes, whereas the equivalent flow and commands in jj would allow you to get those contents back.

Re: Jujutsu at Google [video]

#109

Earlier quoted context omitted.

No LFS, submodules, hooks, or new tags means jj has some ways to go before it is a viable replacement for many organizations https://jj-vcs.github.io/jj/latest/git-compatibility/

LFS sorta works and submodules are just managed by git, and you can create tags with the git CLI just fine. Hooks are a bigger change, though, for sure.

Sounds like I still need git for much of this, so jj and the things it does is and additional thing to manage. I've been told intermixing them is not a good idea

Re: Jujutsu at Google [video]

#110

Earlier quoted context omitted.

LFS sorta works and submodules are just managed by git, and you can create tags with the git CLI just fine. Hooks are a bigger change, though, for sure.

Sounds like I still need git for much of this, so jj and the things it does is and additional thing to manage. I've been told intermixing them is not a good idea

Sure. Use the tools you like!

At the same time, not everyone requires those features. All I mean to say is, the degree of support is varied out of the things mentioned, not just "no support for any of them."

It's still pre-1.0 software. We'll get there :)

Post reply on HN