My go to for most of what you mention is Go, but that’s obviously a compiled language and not for scripting. Or is it - What do you think about https://github.com/traefik/yaegi, which provides an interpreter and REPL for Go? It would let you use a performant and well documented language in a more portable scripting way, but not preclude you from generating statically linked binaries if and when that’s convenient.

I mean, I don’t know how comfortable I’d be bringing one to work, but the behavior you’re looking for (complex macros with swappable config files) remind me of pentesting devices like the Rubber Ducky.

deleted by creator

There’s already some good advice here, especially about virtual environments which might be the most important new concept to learn IMO. But just to let you know - it’s not just you. The most generous view of the Python package situation is that there are a lot of different ways to do it.

a stable experience that isn’t buggy

Stable has a particular meaning with distros but I think the context here is using the plain English definition of the word.

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

The README lacks a description of why I would choose this over rm. The name makes me think it might replace shred but that doesn’t appear to be the case.

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.

Rust: “Oh honey you aren’t ready to compile that yet”

“That sign can’t stop me because I can’t read!”

Looks cool! But FYI this site is fucked on mobile (at least iOS), there’s a giant lemmy logo/link that blocks the form fields.

I use wire label stickers. This is exactly what they exist for and will be under $10. I have the Klein Tools numbered stickers because my priority was matching ends in a large bundle, not adding informative labels. But the majority of products let you write your own label.

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

Can’t you cut out the battery code since your screenshot indicates it wasn’t used? I should be clear that you’ll have to edit some bash scripts to make what you’re asking for happen.

Looks like that config info might be defined in this script

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 will never use a terminal that requires a subscription to use my own damn computer.

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.