maybe true, but also in my self proclaimed non-keyboard warrior opinion, I think GIMP is a silly name. More so because I am juvenile.
Photoshop is kinda a cool dope name, and unfortunately GIMP is not.
“jj op log” shows you the operation history, which you can then “jj op restore” and point to where you want to restore to :)
(disclaimer: im still jj newbie, but this has gotten me out of the snafus ive put myself into while learning g)
I was always very frustrated with git workflow for working on multiple features/bugfixes simultaneously (multiple branches [1]). Changing between them, or combining them for testing is tedious -- constant stashing, switching, cherry-picking. Conflicts fit very poorly into git's version control model - you can't just tell git to ignore some conflict and continue for the moment so you can take care of it later. You have to stop the thing you wanted to focus on and instead babysit git because it found a conflict. Etc.
These are less of an issue once you've molded yourself to fit into git's strange ways, but jj feels like a much nicer tool -- especially for beginners, but feels like it frees up cognitive space even for more experienced folks. You can focus less on the tool and focus more on what you actually want to do.
[1]: I've tried using multiple working trees, but that workflow never really "stuck" with me.
I've done the multiple trees thing too, and agree it didn't work very well.
jj solved the biggest problem for me, which is how much time you spend rebasing when you have 1 PR = 1 stack of commits on top of main. It's easy enough to work on multiple branches this way, but it's a lot of repeated pain when `main` diverges and your changes on top are still out for review. (I honestly just started squashing all of my commits before review, so I would only have to resolve conflicts once.) jj fixes all of this. I especially enjoy working on a 3rd pending change that refers to the previous 2 pending changes; `jj new june/feature-1 june/feature-2` and then you add feature 3 there. You can even `jj squash --into june/feature-1` if something makes more sense being in a prior commit. It's all very wonderful if you are working with other people and you can't immediately mutate `main` upon finishing some work.
i’ve always been interested in improving the git workflow i have for my small team (usually 2-3 other programmers), i think particularly hopping branches/commits, merging changes, rebasing and reorganizing history, i think git does suffice for that stuff if you know the commands, but jj makes it feel so fluid and easy to do, and having enough depth to get as expressive as you need to be
a lot of other tools ive found were lacking for one reason or another, and mightve not been git compatible. with jj you can hop between git and jj commands as you please, essentially full compatibility with git
I didn’t really have any complaints about git, but people I trust told me to check out jj anyway. Now I’m not going back. Something can still be nicer without another thing having to be bad, basically.
6 frames is not enough to realize you made a typo / read whatever git is outputting telling you that you made a typo, and then respond to that input correctly.
in video games it may seem like a lot of time for a reaction, but a lot of that “reaction time” is based off previous context of the game, visuals and muscle memory and whatnot. If playing street fighter and say youre trying to parry an attack that has a 6 frame startup, you’re already anticipating an attack to “react” to before their attack even starts. When typing git commands, you will never be on that type of alert to anticipate your typos.
To explain the coffee comparisons, people like to buy coffee as a daily expense around the 3-5$. not exclusively starbucks, but it is a part of many people’s routines. so its a useful frame of reference for most people. hope this helps
That “someone” who made the fix for Proximity is Mike Welsh, who created Ruffle! He has done a lot of work for flash preservation and truly cares about Newgrounds and it’s community. Back in 2013 (when he was actually an employee of Newgrounds) he was the sole programmer on Swivel, probably the best swf-to-mp4 converting tools ever. Every animator I know that uses flash STILL use Swivel to get an MP4 export.
Oh man I loved the podcast you did with Mike for Newgrounds. I had never stopped to think about the fact that Mike had to actually write an entire flash emulator to get Castle Crashers to run on the xbox. It's so clever and genius, shipping users an emulator like that.
To anyone who isn't familiar, here's a link to the podcast:
haha thanks! Yeah Mike is a real programming wiz and he’s super inspiring! I’ve gone to him for programming help many times but he always tries to get me to learn it on my own than handholding me… lol. He’s one of the nicest people I know :)
That's really awesome. I don't follow these things often enough anymore, so the name didn't look familiar to me. But I'm glad he's put so much effort into Flash preservation.
