This is exactly why I don't like some people labelling Rust as system programming language when it plays role in many areas. Nice article
Ten years after Rust 1.0, we need to stop thinking of it as just "systems programming." That label carries historic baggage and scares away teams who could benefit from Rust. corrode.dev/blog/foundationa… #rustlang #rust

Jun 7, 2025 · 12:28 AM UTC

13
7
1
120
Replying to @AstraKernel
Just don't care about labels or thoughts from others. You can even ignore my thoughts here. Just use it where you want, that's the only way to discover
1
6
Replying to @AstraKernel
I always thought rust was a general purpose language. That's what is for me at least and where I think rust shines.
1
8
Replying to @AstraKernel
Rust is a general purpose language, can be used in many domains.
1
6
Replying to @AstraKernel
Rust is not just about systems programming, it can be also used for web development too (Axum, Actix Web can be used there).
7
Replying to @AstraKernel
We still call it system programming and everyone knows its roles and wide range of use case
3
Replying to @AstraKernel
yh, rust's honestly so versatile. it's way more than just systems stuff.
1
Replying to @AstraKernel
We are using it for web
1
Replying to @AstraKernel
Never thought of rust as a system programming language tbh. Quite the opposite - more like a Java competitor. Would still prefer c/zig for system/low level things
Replying to @AstraKernel
Not to beat a dead horse but most languages today are “more” than systems languages.
Replying to @AstraKernel
Yeah, I would put it on a layer just above C/C++. For real systems-level bit-banging you would need to go unsafe, and at that point Rust gets a bit messy. Most of my Rust code works on quite an abstracted level (traits, fancy enums, etc.), so high-level use is more prevalent.
Replying to @AstraKernel
You can get decently far with a high level mental model but very quickly you'll need to think in terms of memory management, so I call it a systems pl