Downvote me into oblivion or whatever: It's not relevant to me in the slightest whether you built it in Rust or not, or even Python, Go, Java, Node, PHP etc. There is lots of great and terrible, fast and slow software written in each. OP might only have 3 months of programming experience for all I know.
Why is "made with Rust" any more relevant than "made with Go" to an end user of a software product? It just doesn't matter.
The DevOps team at my company wants to hire a replacement for a very talented engineer. They’ve been interviewing candidates. The board got wind of it and someone not in their team decided they needed an AI Engineer, which is absolutely not what they want. So to release the funds they have been forced to change the job description and go after a different type of role altogether. It’s complete nonsense.
> It's much more comfortable to be the person that "could be X" than to be the person that tries to actually do it.
It’s much more impressive to say you have done something than to say you’re going to do it.
A friend of mine has all these failed hobbies he tells everyone he’s going to do, then gives up on. I wait a few months before telling people I’m doing something so I’m fairly confident it’s something I will carry on.
I’ve been writing Go for nearly 4 years and work on a team with senior Go engineers. Concurrency is the language feature people seem to talk about most when talking about Go, and yet we use it so rarely; usually it’s just a second pass optimisation rather than something thought about from the start.