Comments by "MrAbrazildo" (@MrAbrazildo) on "Google Claims Rust Is As Productive As Golang | Prime Reacts" video.

  1. 0:08, hm... I don't know. I use to fly with C++. Unless Rust dismisses tests, which is not true, I have some doubts... C++ can be felt as slower when typing declarations vs languages that dismiss them, or when those language have an already existing lib/algo to solve things at once. These are the 2 most common cases I can remember now. Other than that, C++ dismisses writing defensive stuff (this should not take too long) and has a concise syntax, that can be even more using macros. Running the app with some inputs known to have certain results, it soon becomes clear if a mistake appears. So stop and fix it. For experts, just by the looks of the bug (from the report), there's ~90% chances to be pointed to the right track of it - yes, almost all bugs are pretty fast to catch, even with manual tests, let alone automatic ones. 3:03, agree. I use only FP, until I find that some variable would potentially create a mess, if changed on the wrong place. Only then I start to use class, to both protect and control that var. This is fast to type (not bloated with unnecessary classes) and easy to test (mostly f()s). And even if an environment of classes state needs to be tested, through macros (plus C++ concise syntax declarations) it's possible to compress wonderfully an entire situation (several classes) in 1 automated test, maybe in a single line, if lucky! And that conciseness encourages to write more tests.
    1