Loading video player...
Like it or not, C++ is never going to
die. Alex, every single chance I get on
Acne News, I say we should just let the
language die. So, I've heard a lot of
complaints about C++. What's your beef
with C++?
>> C++ doesn't give you very much to work
with like package management, sane
runtimes, there's nothing like an IP
address built into the standard library.
There's no networking support. So,
people build their own stuff on top of
it over and over again every other year.
You've got like 17 package managers.
None of them interoperate with each
other. you've got a few de facto run
times and you get more all the time. For
a language like Rust, you got some good
stuff to work with and then you can
actually start building the thing that
you care about instead of designing your
own runtime. I've seen a lot of people
complain though that with Rust, your
code must be perfect to compile, which
is cool and that like there's all sorts
of bugs, memory management stuff and
threading problems that people make in
C++ all the time that are impossible to
make in Rust. But if you're just playing
around, that can be really frustrating.
If you're just trying to try a concept
out, you have to get your code perfect.
If there's a problem like that that
you're facing in C++, you either
shouldn't have written it in C++, you
should have written it in Python. It's
good to do the upfront cost of doing it
the right way. You know, there are some
like baseline issues that you can get
out of the way with something like Rust
that will cost you time and a lot of
money down the line if you can even find
them and actually fix them. It's good to
do things right if you're if you're
writing things like on a systems level,
actually talking to the colonel. But
sometimes I'm goofing around, right? I
just have an idea. Would it be cool if
we did this? And by the time I program
it up, I realize it's a stupid idea.
>> Do it in Python. Don't do that in the
rest. Of course not. Yeah. I mean,
>> that's actually what I do. I actually do
it in Python, but I'm imagining I might
do it in Rust someday. And you're right,
it's not what I do at all.
>> Most problems can be solved with Python.
It's the second best language and
everything.
>> Yeah. So, the problem with Python is
that it's slow. Rust is lightning fast.
>> Yeah. I mean, it's one of the design
goals of the language. Be able to have
tight control over the memory without
blowing yourself up.
>> All right, you win. Let's burn C++ to
the ground.
Come on. If Rust is so great, why is
Speedify written in C++? I don't know.
Oh, was that my what I'm supposed to
say?
>> Oh, I'm like literally asking you.
>> Oh, Beat was started 10 years ago and
Rust wasn't really an option back then,
but maybe it's coming along. We have
some particular requirements that I'm
not totally sure. We're getting there.
In conclusion, I want you to subscribe.
C++ isn’t going anywhere, at least not yet. In this video, Alex and Speedify developer Will take a technical look at C++, Rust, and Python in systems programming. They break down C++’s lack of built-in networking and package management, Rust’s strict compile-time guarantees, and why both still dominate performance-critical software like VPNs and router firmware. They examine how Rust enforces memory safety and concurrency, why Python remains ideal for rapid prototyping, and what “doing it right” means when writing code that talks directly to the kernel. The discussion focuses on runtime design, network stack efficiency, and the real trade-offs between development speed and system control. #techtalk #rust #cplusplus #programmer #softwaredevelopment #programmerhumor