News for hackers. Stuff that matters.
Re:Rust 1.100.0 by benjiro29 on Thursday November 12, 2026 @05:45PM (#50475488)
Is the compiler any faster now?

If your codebase is not some small project, its excruciating slow. Even if you try different linkers, and other compilers, nothing really make incremental compiles eat so much of your system. Even more so if you have multiple AI agents doing security and other checks.

Switched to Go for several months, and the difference was very noticeable. Until you started to get there also 50k+ files that are interlinked. And let us not talk about Go and Rust their issues with insane amount of debug/cache buildup.

Imaging if you have 4 to 6 agents running that, with each seeing the cache grow from 20, 30, 40 ... To the point that a 100/1000GB SSD grows to 800, 900GB usage. Often in barely a day.

Seen my NVME drive its lifespan drop from 98% to 91% in barely a few month time. I dread looking at it again lol

What was the solution? Going back to C ... Despite right now working on a 800k lines project, it compiles way faster the Go, and well, Rust will have pegged all 16 cores for a minute, for EACH agent trying to recompile on a small change.

Memory safety? Instead of checking at compile time, and wasting my time, this has simply been moved to AI agents checking, making tools, checking, at night. So it does not disturb my own work.

Its ironic, how both modern projects, end up being worse off. Best of all, the C project is way faster then the same project in Go and Rust. Yea, it was "fun" having AI transcompile them twice but the difference on actual large codebase, and not some micro benchmarks is not a joke. To the point that now all my projects have gone back to C...

And yea, i expect some fast downvotes by our Rust friends because saying something negative about Rust always gets people downvoted here. No offence but Rust being linked to LLM and the whole checker was a benefit before AI came around. But now you can offload a lot of safety checks to the backend/offhours, instead of paying for it with every compile.

Re:Rust 1.100.0 by benjiro29 on Friday November 13, 2026 @08:46AM (#50483407)
Thanks for proving my point. Every time there is some criticism of Rust, some people can not help downvoting because they associate their being with a programming language. Such odd behavior...
Re:Rust 1.100.0 by amenhotep on Friday November 13, 2026 @12:09PM (#50486476)
I downvoted this post for complaining about downvotes, and, after you called attention to it, went back and downvoted the previous post for preemptively complaining about downvotes. Hope that helps.
Re:Rust 1.100.0 by pdimitar on Saturday November 14, 2026 @12:53AM (#50494407)
IME you're optimizing for the wrong thing and are taking myopic and short-term-pleasure measures.

I too grind my teeth when programs are slow, especially compilers, but Rust has saved my hide enough times that I accept the slowness of the compiler / linker stack as a necessary price for the peace of mind once the program runs in production.

Plus, they're working on it all the time. Too slow for my taste? Definitely. But it's still okay.

...And stop blaming downvotes on Rust criticisms. You're 10x more likely to get downvoted for attacking an imaginary group or generally sounding like you're flaming.

I found your comment interesting almost until the end, and then I rolled my eyes hard at the final part. Just don't. Keep criticisms informed and you'll get much more interesting replies and reactions.

Seriously. Try it.

(And don't double down on a victim complex either; i.e. your smaller comment under the bigger one.)