Length might have mattered in the 80s and 90s when IDEs were crap but we got autocomplete in pretty much all our text editors (even TUI ones like vim).

As for readability there is an argument to be had in specific contexts, but 9 out of 10 times it makes more sense to use a proper word.

Example:

let list = [1, 2, 3];
for i in list {
    println!("{}", i);
}

In this case using item in the place of i would be more fitting.

I’ve been using keepassxc for a while now and it’s better than most other options, everything is stored locally and encrypted behind a master password.

All you micht want to do is make a backup of your vault onto an external drive (best practice would be encrypted via the options you have, I use luks because I’m a Linux nerd).

I highly recommend you give it a shot, it’s a modern day programming language with high level features and the speed of C that encourages memory safe code and gives you the option not to if there is something you need to do that doesn’t adhere to its rules.

Rust can be verbose at times though, but it helps make sure you know what a function takes and how it returns data. It even has the fastest regex library on the planet thanks to it’s extensive type system.

If you want to get started their book has you covered and will guide you through the basics, or you can try rustlings for a more hands on approach.

Lastly I will recommend you check out “no boilerplate” on YouTube if you want a nice video series on the various things in rust and how they are there to help you.

I suggest you give rust a shot then, they made their compiler produce meaningful errors with suggestions on how to fix your code and due to its restrictiveness many runtime errors become compiler errors.