This is hard to say without knowing the use of the scripts. If it's something to be used as normal CLI tools, probably some place that's in the user's path. If it's something else, I would just have it download to the current working directory so that the user has the choice on where to put it.
I have games installed but I mostly just write programs for fun now. I usually don't get a ton of time to play games, plus they haven't been as fun as they used to be as a kid.
This sounds amazing! I will also put here there's also chronometer that has a lot of the same functionality as fitnesspal but without the subscription, but you have to use an account.
Reading the rust book is a great use of your time. Rawdogging is a good method if you're just concerned with things you're working on. You can also read documentation on different things that you may not be working on, but know is a gap in knowledge. For me that was the async and tokio books as async rust is a bitch.
A lot of rust libraries use the same approach by having some type of "book" for documentation. I treat them like normal reading, so I'll be out and about or just sitting and I'll pull one out and read it leisurely. It's another way I've found to learn by osmosis. Doesn't even have to be something I'm working on, just something interesting. It sounds like you're doing what interests you, and that's what's important.
I've been thinking about trying to make plugins for awhile (which is the most relevant thing I can say). This looks really cool and seems like it'd be a nice start into audio programming.
I think one thing to mention is that Rust is highly specific in what it does. In most of the examples you mentioned, string types, tokio::main, you can essentially just say that rust is more explicit. When initializing an integer variable in C using int, it's not specified what use the integer is or whether it's signed or not. i32, uint16_t you can see how it's specified. Using tokio::main before your main function just specifies that you're using the tokio asynchronous executor for your async code. In the case of string types, they all have different implementations which just help with being specific.
The reason I like Rust is because I know what's happening when I read it. Did I have to read the whole async book to understand how the tokio::main stuff works? Yes. But now I understand exactly how it works. The problem I have with using Javascript is that it doesn't have that high amount of explicitness(is that a word?). At the end of the day, if you're using it for a personal project or you're arguing for language supremacy, it really just comes down to personal preference.
Is anyone actually going to go and check what they asked for? I feel like I understood what they asked but still don't know where to start if I were to try.
This might be dumb, but what if you used parsec on the other machine?