this post was submitted on 13 Nov 2026
75 points (100.0% liked)

Programming

29288 readers
393 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] truthfultemporarily@feddit.org 1 points 3 days ago (3 children)

Is it really necessary to keep adding features? Where is the place for C++ anyway when rust exists?

[โ€“] lemmybeyourfwend@lemmy.org 1 points 8 hours ago

Difficult to erase entire products and projects built around C++ from one day to another. Yes, Rust is awesome and so is C++, they both have a place in this world ๐Ÿค—

[โ€“] thingsiplay@lemmy.ml 6 points 3 days ago

There are more experts and code in C++ than Rust. The entire world runs in C and C++. So working on those languages and expanding or refining them makes sense. Even if Rust takes over the world and is more used than C++ in the future (if that happens ever), it would still make to maintain and refine the language. Not everyone likes or wants to use Rust.

[โ€“] BeigeAgenda@lemmy.ca 5 points 3 days ago (1 children)

Even if we include LLMs porting code, the sheer amount of c++ code makes it not worth porting, and some legacy code just need occasional updates, especially embedded.

I expect that even if porting becomes free, perfect and instantaneous, there will be plenty old c/c++ code around for decades.

[โ€“] HaraldvonBlauzahn@feddit.org 4 points 3 days ago* (last edited 3 days ago)

Even if we include LLMs porting code, the sheer amount of c++ code makes it not worth porting, and some legacy code just need occasional updates, especially embedded.

It is more effective not to port old working code, which would cost a lot of resources, but to write new code in Rust, where this is possible. There have been a few studies on this, even from companies like Google. The thing is that new code is more likely to have bugs than working old code. So, spending effort on new code gives more safety for a given amount of effort and resources.

On the other hand, it absolutely makes sense to write completely new projects in Rust, if the needed library support is there, since Rust tends to be more productive.

Also, in embedded systems, space systems, systems with certification requirements and so on, Rust is making inroads. Though these are rather conservative areas where tools are not changed quickly.