| > but I don’t think it’s the right tradeoff in all cases, especially not in startups where velocity is crucial This could be true for C++, Java or maybe C#. Against them, python/ruby run circles. But Rust change the equation. Is super-productive... BUT what is important to note is that you need developers that have done the initial climb and go fully rust with it. After this, things start to click neatly: - Modeling code is easy & fast - Composing code, flow! - Testing (all of it, including benchmarking and integration) flow. - Refactoring (big!) is super-easy. This one is where the "velocity" is actually need. But you CAN'T "code fast". You CAN'T skip in good practiques "let's ignore the use of clippy, Result, proper use of traits (like Into/From), etc". (and even write documentation with including doc-test!) This is where the "I write code FAASSST bro!, not time for pesky good practiques!" get hurt with Rust. You need to buy the whole package, because Rust is MADE to be used fully in harmony. And when you finally do it. IS FAST TO CODE. And even FASTER to refactor. And probably so minimal post-fixes. --- P.D: Major blow against Rust? Slow compiling. This is the one factor that blow the dream and where you truly need a decent machine and flow to make it nice. However, if you take the above advice, you are already with Test/DocTest/Clippy/Check flow and that part can be done to be efficient. |