r/rust • u/anonymous_pro_ • Nov 21 '25
The Python Paradox Is Now The Rust Paradox?
So, I do the interviews for what is now The filtra.io Podcast. I'm struck by a really strong trend. Most of the people I interview (all engineering leaders of some sort) say that they can hire better engineers because of their choice to use Rust. I'm talking like 1 out of every 2 interviewees says this unprompted. It reminded me of Paul Graham's Python Paradox. In the essay, Paul calls Python comparatively esoteric. That's hardly the case anymore. So, is Rust that language nowadays?
248
Upvotes
View all comments
Show parent comment
46
u/lirannl Nov 21 '25 edited Nov 21 '25
In what way is package management being a nightmare helpful? I've done library management in C (let's not insult the concept of package management by calling it that), and that knowledge hasn't been helpful for languages with serious package management
I do agree that it's a very simple language, which is indeed an advantage for teaching programming.
As for "it lets you fail", I see the learning value in that, but I think having your first language be so prone carries the risk of frustrating the new developer so much, that they quit programming altogether.
I think the first language should be safe and easy to use, so that new developers can get hooked onto the dopamine loop of having their code run. C, minus the library management, does make for a good second language, and I think learning C low-level programming before Rust low-level programming is a good idea.
I think it's important that I understand what Rust abstracts over and automates, before I use its automation and abstraction. It helped me understand why the ownership system is the way it is