It is inevitable, Rust is poised to obliterate C++ as the systems programming language of choice, and the writing is already carved into the silicon. C++ has become a grotesque relic of committee-driven bloat, drowning in its own incoherent patchwork of legacy syntax, undefined behavior, and bolted-on features that pretend to be “modern”. The so-called “modern” C++ standard library is a monument to verbosity and inefficiency, riddled with leaky abstractions, footguns, and template metaprogramming monstrosities that make even seasoned engineers weep. Memory safety? Rust bakes it into the type system. Zero-cost abstractions? Rust doesn’t just promise them.. it enforces them with rigor. Every new “feature” C++ adopts is a pale, twisted shadow of something Rust already did better, cleaner, and with compile-time guarantees. C++ isn’t even fast anymore - modern compilers wade through layers of STL and virtual dispatch hell to produce binaries that barely edge out managed runtimes like C# or JVM-based languages. Meanwhile, Rust compiles to lean, predictable machine code, driven by fearless concurrency and ownership semantics that make segfaults and data races relics of a less enlightened age. The age of Rust is not coming... it has already begun, and C++ is staggering, bloated and broken, into irrelevance.

>>105616043 (OP)
retvrn to c

>>105616043 (OP)
The best argument against rust is that you need to shill it
t. pony gang

>>105616043 (OP)
Where can I learn concurrency in Rust?

>>105616184
you cant lol there isnt one

>>105616184
https://doc.rust-lang.org/book/ch16-00-concurrency.html

>>105616043 (OP)
In my company, the upper management doesn't even allow the use of C++ is any new projects, C++ is a legacy language now.

>>105616187
Of course there is. It's just bad because lifetimes and ownership make it programmings equivalent to cock and ball torture. As far as I can tell most people just either stick to single threaded Rust or use a runtime like Tokio, or a library Rayon to do anything parallel in Rust (Rayon is a pretty impressive bit of kit imo).

>>105616043 (OP)
It's good that C++ is being forced to clean up or die. Personally I think Zig will take the crown when it's all said and done because I can't imagine all the autists that love system programming will willingly give up control and bow to the borrow checker like Rusts demands.

>>105616043 (OP)
How do I make a linked list? A graph?

>>105616272
You're one google search or LLM query away from your answer. There's no point in spoonfeeding anyone on basic stuff.

>>105616043 (OP)

>>105616411
fyi, the answer is one of "use unsafe" or "don't do that" depending on who you ask.

>>105616043 (OP)
>It's time to lean Rust
>It's time to lean
>Lean
Stop yapping about borrow checkers and get a spell checker nigga.

>>105616043 (OP)
this douche used elipsis unironically... lmao!

>>105616043 (OP)
C and C++ shills are accelerating the demise of C and C++. They are bad people who are willing to lie in order to prevent better technology from succeeding, and that's nothing new. They were doing it in the 80s with Lisp, Ada, Pascal, and a lot of other languages. The difference is that back then a lot of that technology was expensive, so the C/C++ shills could get away with lying about something most people never used, but now all these languages are free and you can download them and see for yourself.

AI generated OP

>>105616272
>linked list?
struct Node<T> {
next: Option<Box<T>>,
value: T,
}

>>105616648
>Option<Box<T>>
Should be Option<Box<Node<T>>>

>>105616043 (OP)
>>105616224
>>105616249

>>105616767
lol I've not seen that one

>>105616043 (OP)
>useless CoC and politics block your path
no thanks