4 ms·
Speak for yourself: I'm not returning to the world of "discipline" (aka lost productivity) without a damn good reason to carry on existing codebases. It's just
by BanTheBastards 3y ago
Speak for yourself: I'm not returning to the world of "discipline" (aka lost productivity) without a damn good reason to carry on existing codebases. It's just a waste of a good coder and certainly of good time.
- Jyaif 3y agoIn C++ discipline is optional. In Rust it's mandatory.
- timw4mail 3y agoIn C++ crashing with a helpful error is rare. In Rust it's rare not to get a helpful error.
- BanTheBastards 3y agoI completely disagree; discipline is only optional in C++ if you want to ship broken code. Even the top poster in this thread that actually cops to the productivity overhead of C++ admits (albeit obliquely) they still make memory errors
- steveklabnik 3y agoI think this is amusing because both directions completely work: In C++, you can do whatever. Rust forces you do to some things. No discipline required by C++, absolutely required by Rust. In C++, you can do whatever. Rust forces you to do some things. This means you must have discipline in C++, or you will do bad things. But in Rust, you can do whatever you want, the compiler has your back.
- Jyaif 3y agoGood point, I was imprecise. I should have said that no discipline is required in C++ to obtain a binary.