News for hackers. Stuff that matters.
Re:A review after using Rust on embedded in production for o... by nicoburns on Monday October 14, 2024 @04:52AM (#41835570)
> I recently finished a contract at a (very large game dev) company where some tools were written in Rust. The tools were a re-write of python scripts and added no new functionality but were slightly faster in Rust. > The reality was that these tools were unmaintainable by the rest of the company. Only the author "knew" Rust and it was hard to justify a new hire Rust developer to maintain this small set of tools.

I can believe this, but it's funny because I work on a project where the main product is written in Rust, and it's the build tools written in Python that are the technical debt that nobody really wants to touch! In our case I suspect rewriting them in Rust will end up being the right thing to do (if/when we can justify the switching costs).

Re:A review after using Rust on embedded in production for o... by Seattle3503 on Monday October 14, 2024 @05:40AM (#41835864)
That makes sense, as the bulk of your developers are probably Rust devs. Homogeneity favors Rust in this case. Also Rusts existing build system is (unsurprisingly) built around Rust, so it makes sense to keep with it.
Re:A review after using Rust on embedded in production for o... by cypressious on Monday October 14, 2024 @06:58AM (#41836332)
I really enjoy projects where the project and the scripts around it use the same language.
Re:A review after using Rust on embedded in production for o... by blandflakes on Monday October 14, 2024 @07:20PM (#41843246)
I find that sticking to a single stack is severely underrated.
Re:A review after using Rust on embedded in production for o... by bsnnkv on Monday October 14, 2024 @11:32AM (#41838458)
> I can believe this, but it's funny because I work on a project where the main product is written in Rust, and it's the build tools written in Python that are the technical debt that nobody really wants to touch!

Oh hi! You must be my teammate!

I joined a team like this and just started a personal build/dev/ops tool repo in Rust for things that I needed but were not automated. Over time it has become an "official" repo and renamed to be blessed with an official "org" package prefix.

When I started this project and people were interested, I was asked why I didn't just add to the Python repo; I said that others are free to rewrite them if they want to, but I can't justify spending days messing around with Python to achieve what I can in less than 30 minutes with Rust when I need to quickly automate a tedious task.