The presentation software itself (Excalidraw) makes this nearly unusable for me:
When it opened up the entire left-half of my screen is blank, and the diagrams are obviously cut off on the right. There is no apparent way to scroll horizontally (excepting a mouse with a horizontal scroll mechanism of some sort): There is no horizontal scroll bar and neither the arrow-keys nor click-and-drag serve to scroll horizontally. Zooming out made things a bit clear what was going on, (margin notes shifted the content far to the right).
Maybe I'm out of the loop here, but scanning over this I can't help but ask myself: "Why Jujutsu?"
I don't understand what the point is over just using git. The top intro defined some JJ names for git things, but it's not clear why I would want or need this. What problem does it solve with using git?
Ideally, reduces cognitive complexity because you don't have to think about the staging area anymore, just commits.
I recently started trying it out at work and I like how fluent it makes what would be more advanced git operations like squashing and rebasing.
Issues I've run into have been understanding its version of branches (bookmarks), understanding its merge conflict indicators, and its lack of respect for git skip-worktree.
> Ideally, reduces cognitive complexity because you don't have to think about the staging area anymore, just commits.
This is the thing I don't like about jj. I know it makes splitting easy, but splitting is harder than selectively adding after blindly merging all changes.
The presentation software itself (Excalidraw) makes this nearly unusable for me:
When it opened up the entire left-half of my screen is blank, and the diagrams are obviously cut off on the right. There is no apparent way to scroll horizontally (excepting a mouse with a horizontal scroll mechanism of some sort): There is no horizontal scroll bar and neither the arrow-keys nor click-and-drag serve to scroll horizontally. Zooming out made things a bit clear what was going on, (margin notes shifted the content far to the right).
Firefox, 1920x1200 screen.
Imgur Link https://imgur.com/a/iYKxSQu
Thanks!
Maybe I'm out of the loop here, but scanning over this I can't help but ask myself: "Why Jujutsu?"
I don't understand what the point is over just using git. The top intro defined some JJ names for git things, but it's not clear why I would want or need this. What problem does it solve with using git?
Ideally, reduces cognitive complexity because you don't have to think about the staging area anymore, just commits.
I recently started trying it out at work and I like how fluent it makes what would be more advanced git operations like squashing and rebasing.
Issues I've run into have been understanding its version of branches (bookmarks), understanding its merge conflict indicators, and its lack of respect for git skip-worktree.
> Ideally, reduces cognitive complexity because you don't have to think about the staging area anymore, just commits.
This is the thing I don't like about jj. I know it makes splitting easy, but splitting is harder than selectively adding after blindly merging all changes.