He needs someone like you for sure. It seems a lot of people who get radicalized double down so hard they lose their friends and family and then can only justify doubling down further due to the Sunken Cost fallacy.
It’s like with flat earthers: “well I stopped talking to everyone I cared about over this so if it’s not true then that was all for nothing”
That’s silly. I’ve never seen comments even as a way to explain what your code is doing (the code often does do that anyway). It’s important to say WHY you’re doing it the way you are.
That way anyone else who comes in there can have the same context you did when you implemented it, which imo is where most bugs occur. People don’t realize what assumptions you made when it was first written, and then make their own (which can easily clash).
It takes work for sure, but admittedly I didn’t find it that much of an undertaking. I’m writing a highly-parallelized 3d game engine with async/await. Am up to a few thousand lines and it’s running very efficiently.
It’s been pretty care-free so far. The biggest pain-point was starting before async traits were stabilized. I think a lack of good instructional material is what has hindered it the most.
This isn’t really true though. Rust has integrated versioning and it cordons things off between editions. If you’re within the same edition, you get updates without breaking changes. Even if you aren’t in the same edition, you can grab specific compiler versions. Granted, in these circumstances you won’t get security updates, but you have to be very out of date for that to be a problem.
I wrote an app using brand new Rust features for work 2 years ago. Despite upgrading the compiler version several times, I never needed to make a single code change. It is still being used daily as well.