Live data from Hacker News

Jujutsu – A Git-compatible DVCS that is both simple and powerful

github.com

31–40 of 233 posts

Re: Jujutsu – A Git-compatible DVCS that is both simple and powerful

#31
post #15

For those that didn't look, this is 100% rust.

Seems irrelevant to me. Why do you care about the language choice?

On the negative side: In some environments it’s a hurdle to build programs in Rust.

On the positive side: It signifies a certain likelihood of memory and data safety that you won’t get in most other languages.

Re: Jujutsu – A Git-compatible DVCS that is both simple and powerful

#33
post #15

For those that didn't look, this is 100% rust.

Seems irrelevant to me. Why do you care about the language choice?

Language matters quite a bit to those considering contributing. It also provides some context for expectations about performance and reliability thanks to language idioms, features and culture.

Re: Jujutsu – A Git-compatible DVCS that is both simple and powerful

#34
post #15

For those that didn't look, this is 100% rust.

Seems irrelevant to me. Why do you care about the language choice?

Because it's trendy to praise brushes instead of paintings, vinyl pressing quality instead of music, and languages instead of software these days.

Jean Baudrillard would call it another level of simulation.

Re: Jujutsu – A Git-compatible DVCS that is both simple and powerful

#36
post #11

Earlier quoted context omitted.

The index is mostly useful to me to split a commit in multiple ones. You do that with a sequence of "git add -p" and "git commit" commands. I am interested in how to do this with jj, because otherwise it looks like a very interesting tool.

> I am interested in how to do this with jj `jj split -r `, where ` ` may be the working copy commit (which is the default). See https://github.com/martinvonz/jj/blob/main/docs/git-comparis... for more examples.

so just for understanding: repeated `git add -p` followed by a `git commit` turns into repeated `jj split; jj squash`, since you create a commit each time?

Re: Jujutsu – A Git-compatible DVCS that is both simple and powerful

#37

Earlier quoted context omitted.

Seems irrelevant to me. Why do you care about the language choice?

Language matters quite a bit to those considering contributing. It also provides some context for expectations about performance and reliability thanks to language idioms, features and culture.

But the info is right on the linked page. Somehow I don't think people who haven't even followed the submission link aren't the ones to worry about yet for "potential contributor".

Re: Jujutsu – A Git-compatible DVCS that is both simple and powerful

#38
This seems really nice.

git got the data model really right, and the user space really wrong. The data model is more important than the user space.

This is the first project I've seen which appears to understand and respect /how/ and /why/ the git data model is so elegant.

Re: Jujutsu – A Git-compatible DVCS that is both simple and powerful

#39

> It combines features from Git (data model, speed), Mercurial (anonymous branching, simple CLI free from "the index", revsets, powerful history-rewriting), and Pijul/Darcs (first-class conflicts), with features not found in either of them (working-copy-as-a-commit, undo functionality, automatic rebase, safe replication via rsync, Dropbox, or distributed file system). You lost me at "free from the index". The index i…

> You lost me at "free from the index". If you click the link that text points you to (i.e. https://github.com/martinvonz/jj/blob/main/docs/git-comparis... ), there's an explanation there for how to achieve the same workflows. I get that it's different , but I don't think it's worse. I consider myself a (former) git power user (I think I have ~90 patches in Git itself) and I've never missed the index since I switched…

Something that’s backend compatible with Git but uses some of Mercurial’s sensibilities?

Sign me up!

Re: Jujutsu – A Git-compatible DVCS that is both simple and powerful

#40
post #3

This looks interesting and I'm glad to see that people are not viewing SCM as a solved issue. While I don't think I'd use this on professional projects yet I'm interested at looking at this for personal projects since I can use the Git back-end and continue to use Github to host my code. I feel like Git has become such a DeFacto standard that nothing is going to replace it any time soon. I've been programming for lon…

I remember that well too (along with Rational Clearcase), and you may totally be right, but git does feel different because it works so well with all sorts of projects, big and small. There were always operations that required hacks. With git that doesn't feel the case to me,perhaps with one exception (but I don't think this is git's fault as much as it's mine for not knowing git well enough to use the tools it provi…

I totally agree. Back when I used Subversion it felt to me like there obviously must be a better way to version control and that the tool got in my way all the time. Git on the other hand almost always can solve my problems and while some things could be improved (confusing UX, a bit too complex, plus bad handling of conflicts) it is much closer to the right tool for VCS than Subversion ever was.
Post reply on HN