3 ms·

I can only speak for my experience. I never re-implement working code using new features just because I can. I have enough on my plate to just use the most con

I can only speak for my experience. I never re-implement working code using new features just because I can. I have enough on my plate to just use the most convenient features initially. Over time, especially if I have a performance or code complexity issue will I take the time to read up on and understand new features. My philosophy is: Don't fix what isn't broken. I suspect that might also be the case for most large code bases.

no_wizard 6y ago
For clarification, as I should have mentioned: I am speaking only to code that has one of the following characteristics: 1. It’s new code 2. It’s a significant re-write 3. It’s a substantial refactoring of existing code or a refactor where using one of the newer apis would be trivial (e.g Reflect.apply vs Function.prototype.apply)