2 ms·
> I'd say it might be more accurate to say that Rust makes it harder/less convenient to take out technical debt. I'll disagree with this one. Refactoring old a
by kibwen 8y ago
> I'd say it might be more accurate to say that Rust makes it harder/less convenient to take out technical debt.
I'll disagree with this one. Refactoring old and rarely-touched code is bliss when working under a strong type system, at least relative to dynamic or weakly-typed languages. The key to the timely resolution of technical debt is to allow things to be updated in piecemeal rather than in one enormous burst; this requires solid abstraction boundaries and encapsulation, both of which are provided by types (in addition to other features of a language, such as a module system). The fact that Rust so heavily discourages global state is another point in its favor.
We can agree that there are contexts where correctness is less important than velocity, e.g. prototyping, though languages that front-load correctness at the expense of velocity are going to produce less technical debt in the first place, because the debts can be paid off before they accrue interest.