3 ms·
> More often than not, brand-spanking-new software is written against 30-year-old APIs. Let's assume this is true, brand-spanking new software will be written
by naasking 10y ago
> More often than not, brand-spanking-new software is written against 30-year-old APIs.
Let's assume this is true, brand-spanking new software will be written against 30 year old APIs that have survived 30 years of attacks and audits, but will avoid the ones that have proven vulnerable.
> I'm just less enthused about the prospect of refactoring my codebase once every few months to stay current.
The perception that you need to do this is false. You might feel pressured to refactor simply because of new syntactic improvements that make code clearer (like switching try!() macro to infix ?), but that pressure is a fiction. There's no real need to do it.