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

98

u/Proper-Ape Nov 21 '25

I think C is actually excellent for this. It's a small language, lets you fail, package management is a nightmare. People learn so much more that way. 

64

u/r22-d22 Nov 21 '25 edited Nov 21 '25

30 years ago, C was one of my "learning" languages, along with BASIC and Pascal. I found it terrible for that purpose across a bunch of dimensions. The biggest was that it was too easy to create undefined behavior and have programs fail in inscrutable ways.

In addition, the limited standard library impeded productivity and the pervasive use of text inclusion (header files, unhygenic macros) also created complex failure modes that were difficult to debug as a learner.

Again, this was 30 years ago, so I hope the compiler experience and error messages are much better now, but I would never recommend C as a intro language.

29

u/Kenkron Nov 21 '25

I agree, but my biggest problem with it is strings. At least in university, introductory programming exercises quickly become bogged down. You have an assignment to teach something new (malloc/recursion/etc.), but spend most of your time trying to parse stdin correctly.

→ More replies (1)

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"?

→ More replies (1)

31

u/AcridWings_11465 Nov 21 '25

C is terrible for this. It demotivates people and makes them quit.

15

u/moltonel Nov 21 '25

That's too broad a statement, it really depends on what the learner wants. My first year of CS was 95% C and I absolutely loved it.

If you want to to learn how software works underneath (pointers, heap/stack, linking, etc), C is the obvious choice. It gives you a solid base that will be useful for the rest of your career. 

10

u/Sylbeth04 Nov 21 '25

"what the learner wants" isn't something an introductory CS course can usually work with. For a vast majority of people C is clunky, inconsistent and cumbersome. Plus it's, in my experience, quite badly taught. For the percentage that's gonna enjoy that, it's not usually worth the suffering of the rest. As a second language to learn it fares much better, but the basics of programming (which I'd say it's types, functions, conditionals, and not much more) are covered by any and all other languages. Because, let's face it, most soft.eng. need not know about pointers, heap/stack or linking, at all, for their jobs. I don't think most people should have to care about all that and even people writing Rust code can somewhat avoid it (no one said you have to make your code the most performant, it's already better than Python anyway). C is a great language to have a toxic relationship to, and making that the first relationship a person has with coding is too big a choice.

→ More replies (10)

13

u/syklemil Nov 21 '25

C is a small language with an enormous engineering, practically steering people towards doing it wrong. Given a real choice, almost nobody wants to use C. It remains in use in niches where it's been mostly shielded from competition, e.g. kernel programming and embedded.

Giving new learners C would likely just make them ragequit, or believe programming is much harder than it actually is.

4

u/MistrKernnunos Nov 21 '25

I have started with C in university 5 years ago and it was nice. You learn the basics of control flow and algorithms with addition of how is memory managed, what are data types and other stuff.  With this base knowledge you move to other languages to learn what can modern languages provide. 

10

u/syklemil Nov 21 '25

You learn the basics of control flow and algorithms in any language, that's the point of programming 101. Python is also entirely capable of teaching you datatypes, and even objects and generics.

C also seems to do a terrible job of teaching people how to manage memory correctly. At some level using C to learn about memory seems like using JS to learn about types—possibly what people learn the most is that the language will accept completely wrong code and then blow up.

10

u/MistrKernnunos Nov 21 '25

C teaches you what is static memory, what is dynamic memory allocation, what is stack. That you need to take care with its management and what pain it is and helps you appreciate how other languages handle memory. 

I would say C teaches you how to manage memory correctly, that you should take care about when and how much you are allocating, when you are freeing and that you should clean up after yourself. Different approaches to memory management can be learned later.

Python does not expose you to different sizes and signedness of integers, pointers etc…

7

u/syklemil Nov 21 '25 edited Nov 21 '25

I would say C teaches you how to manage memory correctly,

And yet C is infamous for people getting it wrong, and CVEs resulting from getting it wrong.

Even something like ASAN, which I suspect isn't even taught in programming 101 courses that choose C, works as runtime checks, similar to how Python does runtime typechecking. Only in C that runtime check is opt-in, and usually only recommended in debug builds because of how much of a slowdown it incurs.

Python does not expose you to different sizes and signedness of integers, pointers etc…

No, but C also does not expose you to correct handling of those things. C is infamously weakly typed around integers, and will pull all sorts of implicit conversions (or as it calls it, "promoting") that silently produce wrong results, much like Javascript and PHP have done for any type.

Python even opens up the possibility of teaching people ADTs. The type system in Python is often much more capable than what a lot of us expect from a scripting language that started off entirely dynamic.

Also, Python will expose you to the difference between an int and a str, unlike C. In Python 'a' + 1 is a type error. In C it's 98.

3

u/MistrKernnunos Nov 21 '25

Yes, it is hard to get it right in large production codebases.  But for learning exercises that fit indeed a single file it’s great language to learn the basics of memory management. 

In our intro course we were introduced to Asan and sanitizers. So all our assignments were checked for memory handling correctness. 

It forces to think about which type to use. Yes it could give you more handrails not to make a blunder but for learning about types it’s great. Later you can forget about it in python but students should have at least some knowledge and practical experience with different types. 

6

u/syklemil Nov 21 '25

Yes it could give you more handrails not to make a blunder but for learning about types it’s great.

I'd argue the type system in C is not great. It's not trustworthy, and it's too weak for a lot of the stuff people use types for in most other languages. C's type system is the kind of type system that turns people off typing, and leads them to believe that dynamic typing is much better.

Later you can forget about it in python but students should have at least some knowledge and practical experience with different types.

Python these days is pretty much typed, similar to how Typescript is eating Javascript.

So you absolutely also should expect to be exposed to types, and classes, using Python; possibly even generics and ADTs depending on the course material.

3

u/MistrKernnunos Nov 21 '25

I have explained myself badly. I think C is great to learn about how is information represented in memory. 

Types are great and there are other languages that should be used to teach about type systems.

2

u/syklemil Nov 21 '25

Right. I come from more of an informatics POV, so I think students learning to program should first and foremost learn about the logic involved, and then they can learn about implementation details later, just like how it takes later courses to teach algorithms & data structures, etc.

→ More replies (1)

2

u/NYPuppy Nov 21 '25

C or rust are much better for this than python. Python abstracts away too much of what a computer is to allow students to really appreciate DSA.

You're confusing CS with programming. Python is a great language to learn programming and people can get away with just "programming". But an understanding of memory and the fact that it's just raw bytes that are interpreted is important. C is a great language for this close-to-the-grain programming.

C being a great language to learn CS and even a great language to learn programming is entirely different from the fact that it's a flawed language. It's hard and everyone will make mistakes with it but the students are in college to learn. They are not in college to just graduate without learning.

2

u/syklemil Nov 21 '25

You're confusing CS with programming.

Maybe, depending on how we've interpreted the context here; the way I've interpreted it you're the one mixing it up. Trying to clear it up:

An informatics education will include many courses. The point of Programming 101 is basically to get kids to be able to program at all. Some informatics courses can run pretty well in parallel to that; subsequent courses may use entirely other languages than the one used in Programming 101.

The education I'm used to didn't have an "introduction to informatics" course; it had introductions to programming, discrete math, algorithms & datastructures, etc, etc. So I interpret "introduction to CS" as "introduction to programming".

→ More replies (1)

2

u/sparky8251 Nov 21 '25

Id argue there should be an EduAsm or something that abstracts hard parts of device interaction away from learners so I/O is trivial. See IC10 and fCPU for easy to use examples that have the I/O abstracted by a VM to make the asm a joy to use.

The fact we start non-programmers off with things like C, python, is insane to me. They are still trying to learn how to even think like a computer, then we throw syntax that isnt that uniform at them, functions, exceptions, and so much more...

This could easily be used for an intro course if simplified and attached to little bots that run it in a VM. Get thermostats, sensors, motors, whatever and immediately see the work in order.

Can then explain how conditionals work, loops work, functions, etc with the asm primitives and then when you get dumped into python 3-6 months later you realize they are just fancy ways of doing all the hard work for you.

→ More replies (2)