See this explanation, this is why.

Yup. Most of my career has been working on embedded realtime software, so interpreted languages are right out and really only C and a subset of C++ are available. I’ve now been using Rust in that way for about nine months now and while the syntax is sometimes silly feeling, being able to not worry about some many other issues has made development much better.

Attacking the messenger because you don't have any good argument against the message?

This is the Linux kernel project, one of the technically most conservative projects in the FLOSS community.

Rust is C++ with nanny nags, and immature libraries, and a lot of improvements that 30+ years of C++ has made obvious today which weren't so obvious back then.

The worst thing about Rust, from my perspective, is that it really seems to push programmers to "multithread all the things" because Rust offers the delusion that you can do that more safely now. Newsflash: all the things do not need to be multithreaded, there's an awful lot of code that's just peachy in a single threaded implementation, thank you very much, and multithreading it is just inviting trouble for no significant gains.

Mostly, a good library on C++ (Qt used to be one of those, but it's started becoming annoying in the past few years) offers a lot of what Rust enforces at the language level. Stick to the library implementations and you're safe. Color outside the lines when the library isn't up to what you need - but do so carefully.

I find it insane to have to wait minutes to see the changes and to iterate.

i did devops between 2015 & 2025 and got used to the cadence of waiting between 15 & 180 minutes for testing/production pipelines to finish vetting the work i submitted to them.

i went back to doing IT last year and setup similar pipelines to update the code base my predecessor left behind and my new boss expressed the same consternation about waiting for your changes to iterate.

i'm thankful for it because it gives me 30-ish minute windows to browse and annoy people on lemmy throughout the day. lol

Five minutes with build cache? Or from cold build?

With cache, then there's almost certainly something wrong with your computer or project.

Also... you aren't building with --release every time are you?

5 minutes sounds like way too much, unless you mean a fresh compile. But then you shouldn't need to wait that long between changes, since incremental compilation should kick in then.

And like sure you can break shit up into crates to speed up compilation, but to do that you already have to have a design you're happy with and that's stable.

I mean, if you have your modules structured in a tree structure and with proper visibility, then it isn't a particularly big leap to put it into a separate crate. You just move the files, maybe fix some visibility modifiers still, and then a bit of boilerplate to add it to the workspace.

It's only really when you're publishing to crates.io, that you don't particularly want to keep changing the names/scopes of the crates, as they'll stick around on there for the foreseeable future.

mold and sccache help a lot with the compile times