Me too! I am not a professional but audio support is such a point of friction for me that I’d love to see how others handle it when it’s critical to their work.

Very impressive!

This change would also be bad for anything that scans for keywords, which includes most applicant tracking software.

Can we talk about how utterly absurd it is that there isn’t an obvious answer to this question yet? Feels like we’ve gone backwards from the AIM Direct Connect of old.

So, only about a decade until reaching feature parity with something like lazygit?

Interesting project but this write-up has a bizarre focus on number of lines of code, which doesn’t appear to differ substantially between the two approaches.

RE your edit: I also support that conclusion and I’m glad you’ll give it a shot yourself. A mindset that helps me is this: commenting is part of the iterative code writing process. When I’m struggling to put a concise and understandable comment above some code, it almost universally means that there’s something about the code itself I should arrange more clearly. This is your chance to do some rubber ducking, it’s valuable to both you and the next person to read your code!

You joke but comic mono is startlingly easy to look at…

I could redraw this whole chart using only references to pipenv based on my experiences with managing it alongside other tools (especially homebrew). It’s good at many things but is no magic bullet.