3 ms·

Yes! Ive been working mostly in rust recently for robotics projects. The amount of time our industry wastes on C++isms is ridiculous where rust just works. Unfo

Yes! Ive been working mostly in rust recently for robotics projects. The amount of time our industry wastes on C++isms is ridiculous where rust just works. Unfortunately theres an old guard that refuses to let up and invest in rust. Tbh there is a huge industry aroumd C++ robotics code so I can see why.

iExploder 3y ago
Companies barely have enough time and money to keep developing their already existing 10+ yrs old tested and "working" codebases as is, how would anyone switch to a whole new language at this point?
- abricq 3y ago
  Maybe not converting legacy code, but starting new projects in Rust ! At my robotics company (where I lost so many hours compiling overly-templated code in C++), I was able to convince my boss to start a new small product in Rust (was an internal simulation tool) and it convinced him to let me work on another new product a few month later, also in Rust, on a much bigger scale. He had only ever worked in C++ before, and I guess he doesn't mind to loose hours compiling and fixing memory leaks. But regardless, it worked and now I can work (a bit) in Rust.
  - robertlagrant 3y ago
    That's great - I mostly work in Python now and I came from the Java world. My first paid Python project was from that time - a little data munging script I was allowed to write in Python.
  - accurrent 3y ago
    Im in a similar position to you. My manager loves rust, so Im fortunate... Weve been developing new tools in rust. Some greybeards actively oppose it though. Im not asking for rewrites but at least new stuff should be written with more modern tools. Rust aint perfect but its hell of a lot better than C++ and CMake magic. My experience has been we can build features far faster with rust than C++ and we deal with legitemate bugs not "which idiot forgot to check the bounds of this array?". I think the biggest pitfall for rust howver is its difficulty in interoping with C++ and the unstable ABI (given how much the robotics community love C++ plugins...).
throw10920 3y ago
> The amount of time our industry wastes on C++isms is ridiculous where rust just works. This implies that Rust doesn't have any problems, which is...crazy. In addition to the problematic community, just rearchitecting your code to fit around the borrow checker can be a massive amount of work, which already makes it infeasible for use in some places where the primary work is not on greenfield projects but on legacy code. > Unfortunately theres an old guard that refuses to let up and invest in rust. ...and this is just emotionally manipulative, in addition to incredibly dishonest about the problems that Rust actually has.

iExploder 3y ago

Companies barely have enough time and money to keep developing their already existing 10+ yrs old tested and "working" codebases as is, how would anyone switch to a whole new language at this point?

abricq 3y ago
Maybe not converting legacy code, but starting new projects in Rust ! At my robotics company (where I lost so many hours compiling overly-templated code in C++), I was able to convince my boss to start a new small product in Rust (was an internal simulation tool) and it convinced him to let me work on another new product a few month later, also in Rust, on a much bigger scale. He had only ever worked in C++ before, and I guess he doesn't mind to loose hours compiling and fixing memory leaks. But regardless, it worked and now I can work (a bit) in Rust.
- robertlagrant 3y ago
  That's great - I mostly work in Python now and I came from the Java world. My first paid Python project was from that time - a little data munging script I was allowed to write in Python.
- accurrent 3y ago
  Im in a similar position to you. My manager loves rust, so Im fortunate... Weve been developing new tools in rust. Some greybeards actively oppose it though. Im not asking for rewrites but at least new stuff should be written with more modern tools. Rust aint perfect but its hell of a lot better than C++ and CMake magic. My experience has been we can build features far faster with rust than C++ and we deal with legitemate bugs not "which idiot forgot to check the bounds of this array?". I think the biggest pitfall for rust howver is its difficulty in interoping with C++ and the unstable ABI (given how much the robotics community love C++ plugins...).

throw10920 3y ago

> The amount of time our industry wastes on C++isms is ridiculous where rust just works. This implies that Rust doesn't have any problems, which is...crazy. In addition to the problematic community, just rearchitecting your code to fit around the borrow checker can be a massive amount of work, which already makes it infeasible for use in some places where the primary work is not on greenfield projects but on legacy code. > Unfortunately theres an old guard that refuses to let up and invest in rust. ...and this is just emotionally manipulative, in addition to incredibly dishonest about the problems that Rust actually has.