vl8 VS gitz

Here are a few examples: https://github.com/rec/vl8/blob/main/studies/study1.py

https://github.com/rec/vl8 - the advertisements about what it "can" do are "true", but you can't do any of these things from the command line, it's not at all release worthy.

Here is link number 1 - Previous text "vl8"

I have a alpha-quality system myself for processing audio in numpy buffers called vl8 (getit?).

I'm hoping to fit my newest working project, https://github.com/rec/vl8, into this framework.

Me, I'm a long-time developer with a lot of little production Python libraries and an alpha level audio DSP CLI called VL8, which seems to have almost the same API as PedalBoard's, so I'm thinking of porting it to use that.

When I develop a big feature, I do it on a private branch, and then I commit and push an "anonymous" commit (using this) whenever I have made any progress.

where git st is here (a lot like git status.)

No, there's no reason to preserve commit messages you used during development.

When I am developing, I make many tiny commits with an automatically generated title ('Modify util/files.py') each time my tests pass, or really, when I do anything of value. (I use `git-infer`: https://github.com/rec/gitz/blob/master/git-infer)

This makes it impossible for me to lose work, and acts like a coarse-grained undo for me, where I can quickly move back and forth between spots that the tests worked if I decide I'm going the wrong way, or create a new branch, move back a bit, and make some changes and compare.

_Before anyone sees this code_ I rebase it down to a logical sequence extremely-carefully named and organized commits. (The word "manicured" has been used more than once.)

As I go through code review, I make tiny commits and at the end, rebase them into my carefully-named commits.

I create at least five commit IDs for each final commit I created. No one wants to see these.

I spend considerable time organizing everything so just the information you need to see is in the final commits. All the information should be there.

I have a truly evil command in my gitz package https://github.com/rec/gitz called git adjust.

I have a bunch of git utilities to do common chores, but more, I tend to stack up a lot of commands at once in the command line separated by &&.

This isn't just academic - it affects every git tool. I have a collection of git utilities, fairly high quality, but a lot of my favorite ones don't work over merge commits, not because I was lazy but because I simply couldn't figure out a way to do it that made sense in every case.