Rust is not just beginner unfriendly, rust is also intermediate lvl unfriendly and very hard to read others' code.

But at the same time, I also like it....

Number 4 hit home for me. I've been just trying random shit until it compiles. When it compiles it usually works without understanding what the fuck is going on

Programming rust on an off for 2 years or so

I never used Rust "professionally", I always avoid lifetimes. Borrowing is easy, lifetimes are hell.

4. Wtf is the 'de lifetime in serde deserialize??

Aside from 'static (and the anonymous lifetime '_), the exact name isn't actually meaningful beyond explaining to the reader what you intend to use this lifetime for.

So, whether you call it 'a or 'de or 'database doesn't change anything about the lifetime itself.
Serde calling it the 'de lifetime is just to clarify that this is the lifetime of the deserialized object.

Honestly if you never had to deal with more than one lifetime parameter per function and/or type, good for you! As for what 'de is used for in serde — it’s the lifetime of the data you’re deserializing. It’s not really relevant unless you’re deserializing borrowed data, which is very very rarely the case, especially when it comes to web development which I’m guessing you’re most familiar with

6. What are you talking about, it's always better.

But seriously, I don't have much Rust proficiency and I still pick software in Rust because 1. installing and updating rust itself and things installed with it is a bliss; and 2. the CLI experience of Rust programs tends to be much better than alternatives.

Contrasting that with installing something with Go, which is a common alternative for things written in Rust:

• First, I need Go. So if I chose to install it via another package manager - perhaps with the exception of pacman - I may end up with an out of date version that may cause issues when compiling newer code. I had this happen a few times.
• If I chose to build it myself, first I need an older version of Go to compile a newer Go. Very fun.
• If I chose to install it via their website, it's a manual .tar.gz download and extraction of an executable that doesn't self-update, so next time I not only have to repeat this, but I need to remember it.
• Then there's the gvm project, which promises to resolve some of this friction, and it was my method of choice, but I'm not sure it's maintained anymore and I always have to look up their commands because of things like: gvm list works, but to list versions for download it's gvm listall instead of gvm list --all)

Now for Rust:

• curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs/ | sh
• optional cargo install cargo-update to update everything else with cargo install-update -a

6. I actively chose software written in Rust over other software, even if it's not better, and I argue that it is.

Rust has quite a high barrier for entry which is likely to deter inexperienced developers. I'd say that's enough justification to favour software written in Rust.

Python on the other hand is far too easy to get started with, thus the ecosystem is plagued with terrible software. I avoid it like the plague. Yes, there some decent projects written in Python but they are rare things

How do you feel about Arc<Mutex>? Personally, I just put every variable in an Arc Mutex to make my life easier.