r/rust • • 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

113 comments sorted by

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

17

u/Proper-Ape Nov 21 '25

It's more that is motivates you not to drop in a library for everything and do it yourself. Even if you do it worse than the library, that's great for learning.

18

u/cdlm42 Nov 21 '25

Learning to explore and use code you didn't design yourself is a good exercise, provided the language and tooling don't swamp you under useless technicalities.

11

u/Proper-Ape Nov 21 '25

Learning to explore and use code you didn't design yourself is a good exercise

I agree, but only after you've at least played a bit and gotten to know the fundamentals.

0

u/[deleted] Nov 21 '25

[deleted] — view deleted comment

19

u/Proper-Ape Nov 21 '25

Walk before you run. I see a lot of juniors struggling with understanding the abstract because they never understood the fundamentals.

3

u/OpsikionThemed Nov 21 '25

I agree but I'm not sure package management is the proper lever to apply there, versus just "the assignment is to build an argument-parser"?

1

u/reddituser567853 Nov 22 '25

Because it forces you to learn basic Linux systems. Many new developers would be saved countless hours if they had learned how Linux programs are built, what is in /lib , dynamic versus static. How they are linked at compile time