I'm daily driving Jujutsu, and maybe you should too
drewdevault.com
I'm daily driving Jujutsu, and maybe you should too
1–10 of 50 posts
Re: I'm daily driving Jujutsu, and maybe you should too
#2Why is there no git-light VCS, with only the top 5-8 commands available? Push, fetch, commit, merge, rebase, branch, init... maybe I forget 1 or 2. I have to think extremely hard what command I used intentionally in the past 10 years (sometimes I used some arcane commands, only to fix some problems that was caused by some other arcane commands)
Re: I'm daily driving Jujutsu, and maybe you should too
#3Why is there no git-light VCS, with only the top 5-8 commands available? Push, fetch, commit, merge, rebase, branch, init... maybe I forget 1 or 2. I have to think extremely hard what command I used intentionally in the past 10 years (sometimes I used some arcane commands, only to fix some problems that was caused by some other arcane commands)
There's Openbsd's got[0].
Re: I'm daily driving Jujutsu, and maybe you should too
#4Why is there no git-light VCS, with only the top 5-8 commands available? Push, fetch, commit, merge, rebase, branch, init... maybe I forget 1 or 2. I have to think extremely hard what command I used intentionally in the past 10 years (sometimes I used some arcane commands, only to fix some problems that was caused by some other arcane commands)
There's Openbsd's got[0]. 0. https://gameoftrees.org/index.html
Almost... but not what I'm looking for. I'm looking for something without actual git. I can also just ignore most of the ugly commands of git, but I'm thinking of something that doesn't make me think of what commands are worth remembering. I'm looking for "simple code versioning for dummies, that you can't break even if you tried hard"
Re: I'm daily driving Jujutsu, and maybe you should too
#5Earlier quoted context omitted.
There's Openbsd's got[0]. 0. https://gameoftrees.org/index.html
Almost... but not what I'm looking for. I'm looking for something without actual git. I can also just ignore most of the ugly commands of git, but I'm thinking of something that doesn't make me think of what commands are worth remembering. I'm looking for "simple code versioning for dummies, that you can't break even if you tried hard"
Re: I'm daily driving Jujutsu, and maybe you should too
#6I don't like it, I was expecting something new that replaces Git with a new idea about versioning.
I can already work extremely fast in Git by using bash aliases and my workflow.
This might be useful for those starting out.
Re: I'm daily driving Jujutsu, and maybe you should too
#7Going from changing the code and then describing it to describing your planned change and then implementing it is a good idea.
Now, I just need some GUI indicator or CLI prompt to ensure I don't lose track and I'm good to go!
Re: I'm daily driving Jujutsu, and maybe you should too
#8Why is there no git-light VCS, with only the top 5-8 commands available? Push, fetch, commit, merge, rebase, branch, init... maybe I forget 1 or 2. I have to think extremely hard what command I used intentionally in the past 10 years (sometimes I used some arcane commands, only to fix some problems that was caused by some other arcane commands)
Surely you can just use git and limit yourself to the commands you're comfortable with?
Re: I'm daily driving Jujutsu, and maybe you should too
#9I don't like it, I was expecting something new that replaces Git with a new idea about versioning. I can already work extremely fast in Git by using bash aliases and my workflow. This might be useful for those starting out.
> replaces Git with a new idea about versioning
With the advent of LSP I feel like we're almost to a point where you could version structures and not code. Like being able to follow how some class / method got cut in multiple pieces during a refactoring round.
Or maybe we need something more than plaintext to store code and the meta data around it before we can get to this point. I'm sure it has been already done multiple times in different ecosystems but there must be a way to standardize the information about code and use it in IDE and versioning tools.
Re: I'm daily driving Jujutsu, and maybe you should too
#10I don't like it, I was expecting something new that replaces Git with a new idea about versioning. I can already work extremely fast in Git by using bash aliases and my workflow. This might be useful for those starting out.
Yes, but the usefulness of "something new that replaces Git" would be severely limited by the fact that, well, everybody uses Git. And taking on Git is a task as daunting as, let's say, launching a new mobile OS and wanting to compete with iOS and Android. Jujutsu is gaining traction precisely because it can work on top of a Git repo, so people you are collaborating with don't even have to know that you are using it. Maybe Git experts don't need it, but I am an expert in programming who doesn't want to have to know every idiosyncrasy of the VCS tool I have to use in order to do my job...