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

Jujutsu for busy devs

maddie.wtf

Post reply on HN
Print view View original

81–90 of 552 posts

Re: Jujutsu for busy devs

#81

Post by arp242 »

sunshowers wrote: post #62
arp242 wrote: post #60

Earlier quoted context omitted.

How would that work with applications that hard-code the background to black (or some other colour, like tmux's green statusline)? If you change the colours to work on a light background then those break. You have to choose what you want to break. Once you start pulling on one thread lots of stuff start to unravel. It's really not a simple matter of "choosing a better theme". I've spent a long time looking at this, a…

If you hardcode the background to a fixed color, the 4-bit palette for foreground colors is generally to be avoided -- instead, use the 8-bit (256 color) or bigger palettes.

I don't control these applications.

Re: Jujutsu for busy devs

#82

Post by steveklabnik »

frizlab wrote: post #75
landr0id wrote: post #59

Earlier quoted context omitted.

Honestly one of the biggest selling points of jujutsu for me is its `op log`. You can fuck up your repo in git and that's it -- you're screwed. Or you find some extreme magic on the internet that saves you. With jj you just "jj op undo " and you're fine. Editing prior commits is also pretty easy, which in turn makes fixing merge conflicts pretty easy too.

Like… reflog?

Kinda!

jj has two kinds of these logs: the evolog and the op log.

The git reflog is based on, well, refs. Whenever a ref is updated, you get an entry. This log is per ref. That's HEAD, your branches, your tags, and your stash.

jj's evolog is sorta similar, but also different: it's a log, but per change (think commit in git). This means it is broader than per ref, as it includes not just commits that correspond to a ref, but all of them.

jj's oplog is a log per repository. This lets you do things like `jj undo`, which lets you get the entire repository, not just one ref or commit, back to the previous state, easily.

Re: Jujutsu for busy devs

#83

Post by steveklabnik »

0cf8612b2e1e wrote: post #80
oxidant wrote: post #71

Earlier quoted context omitted.

Counterpoint: Why should my println debugging get committed? They're not "important" for the final product but important for development.

The logic is once you are ready to commit you delete all of the debugging stuff. Otherwise you are committing an illusionary state of the repo that only existed by manipulating the stage. I am a black kettle here as I frequently commit individual lines amongst a sea of changes, but I do appreciate the theoretical stance of jj.

Just to be clear, jj makes it really easy to carry this sort of thing as a separate patch, so while it may be "committed," that doesn't mean it has to go into what you send upstream.

(though for debug printfs in particular, the Right Thing is proper logging with log levels, but I myself love printf debugging and so sometimes don't do that either. Which is why carrying local patches is nice.)

Re: Jujutsu for busy devs

#84

Post by ghoshbishakh »

arp242 wrote: post #27
sunshowers wrote: post #20

Earlier quoted context omitted.

I think jj just uses the 4 bit (16 color) terminal palette, so if a color is unreadable, you can update your terminal theme accordingly.

Some programs set the background colour and some don't. For example pamix sets the background to black, or tmux's statusline, or ngrok. It's not really possible to define one terminal scheme that always works.

So do you suggest we should avoid setting a color in our CLI app? We would take this into consideration in our next pinggy.io CLI update.

Re: Jujutsu for busy devs

#85

Post by forrestthewoods »

stouset wrote: post #33

For anyone who's debating whether or not jj is worth learning, I just want to highlight something. Whenever it comes up on Hacker News, there are generally two camps of people: those who haven't given it a shot yet and those who evangelize it. You will be hard-pressed to find someone who stuck with it for a week and decided to go back to git. You will not find a lot of people who say they switched but just stayed out…

> You will be hard-pressed to find someone who stuck with it for a week and decided to go back to git.

I’ve tried jj on three occasions and I always get confused by something and just bounce. It hasn’t clicked for me.

I’ve only tried it solo hobby projects. For which git is perfectly tolerable.

I have many many many complaints about git. But jj doesn’t move the needle for me.

Reading this post I am extremely annoyed. Almost every single section is “but more on that later”. It’s still far more complicated than it needs to be.

I also really really really hate the jj log rendering. The colors are a sea of barf. Bolding the leading character that represent uniqueness is stupid and adds noise. The username being second is dumb, I almost never care about that. And the bright neon green (empty)(no description set) is such bad spew. Kinda nit picky, but blech.

Jujutsu suffers the same thing Git suffers. Every god damn blog post that tries to explain how simple it is just my eyes gloss over and think “this is too complex for me to care”.

Re: Jujutsu for busy devs

#86

Post by flockonus »

I legit ask myself how many folks avoid Github Desktop for some dogmatic reasoning equivalent to "having an UI makes it worse", when it does the core of common flows extremely easily and clear.

To be clear where it ties to this post: it makes git far more convenient with nearly 0 learning curve.

Re: Jujutsu for busy devs

#87

Post by benoitg »

_bent wrote: post #12

I've been using jj for two weeks now and it's kinda exciting, because for the first time I'm comfortable with using version control just via the command line. With Git I always had to use a GUI (preferably Git Graph in VSCode) and launch all operations by right clicking items, but jj was simple and consistent enough that I could just start using it after reading Steve Klabniks tutorial. The thing I'm running into rig…

I had the same copy paste problem, now I use jjui (https://github.com/idursun/jjui). The daily operations become even smoother, it looks like I’m flying over the log.

Re: Jujutsu for busy devs

#88

Post by Valodim »

0x457 wrote: post #44
stouset wrote: post #33

For anyone who's debating whether or not jj is worth learning, I just want to highlight something. Whenever it comes up on Hacker News, there are generally two camps of people: those who haven't given it a shot yet and those who evangelize it. You will be hard-pressed to find someone who stuck with it for a week and decided to go back to git. You will not find a lot of people who say they switched but just stayed out…

Reason I like git is because I use like 2% of its features. I don't fall for propaganda that I need to use bisect and co. 99% of git commands I call are aliased to 3 characters, so it's dense terminology doesn't bother me.

There were (are?) people who say the same thing about svn

Re: Jujutsu for busy devs

#89

Post by vasco »

flockonus wrote: post #86

I legit ask myself how many folks avoid Github Desktop for some dogmatic reasoning equivalent to "having an UI makes it worse", when it does the core of common flows extremely easily and clear. To be clear where it ties to this post: it makes git far more convenient with nearly 0 learning curve.

Can't be leet like that!

Re: Jujutsu for busy devs

#90

Post by jph »

what wrote: post #40
bravesoul2 wrote: post #21

Earlier quoted context omitted.

Yeah I find abstraction layers suck a bit. Same with miso and uv (for python). They don't "just work TM" and now I have 2 problems. By just work I couldn't install miso onto a fresh Ubuntu without 404 errors and uv kept bitching about my pyproject file instead of just working or trying to fix it. Some of these tools do just work. E.g. nvm seems to just work and is much nicer than raw node installs.

What is miso?

Possibly means mise (https://mise.jdx.dev/) which is a tool similar to uv in the sense of managing versions.
Post reply on HN