News for hackers. Stuff that matters.
Re:A Rust Shaped Hole by imtringued on Thursday July 17, 2025 @06:30AM (#44591708)
Yeah, the thing is, the moment your software has crossed the boundary of success, it becomes a burden, not a blessing. You are now stuck with it and you better have made sure that you're happy with it the way you built it, because you're not moving on from this project any time soon.

Maybe Rust isn't optimized for throwaway projects and that's fine.

Re:A Rust Shaped Hole by ViewTrick1002 on Thursday July 17, 2025 @07:18AM (#44591996)
I think you can do throwaway projects and prototypes about as fast in rust.

But it requires a different mindset which I think many in our industry finds hard to work with. Rust exposes the imperfections rather than hiding them until you explicitly check for them like in most other languages.

Just clone and unwrap liberally and throwaway projects go fast.

Re:A Rust Shaped Hole by blub on Thursday July 17, 2025 @10:26AM (#44593822)
What we’re seeing in practice is not throwaway software but successful companies built over many years using e.g. Golang. When they grow big enough to pay the Rust tax and can’t squeeze more performance out of their set-up they switch to Rust.

Starting something in Rust only makes sense for very few domains and software categories.

Re:A Rust Shaped Hole by gooooood on Thursday July 17, 2025 @11:03AM (#44594178)
I wonder how Go would fare if it had a production-ready LLVM/GCC backend. I wouldn't be surprised if much of the performance differences between Go and C/C++/Rust comes down to optimized codegen (rather than GC, which is what people often complain about Go). Not saying that GC pauses might not be an issue in some cases, but still...