2 ms·
My point isn't so much that ditching the backwards compatibility is always right, even when it lets you shed lots of code, but that you can often massively redu
by vidarh 3y ago
My point isn't so much that ditching the backwards compatibility is always right, even when it lets you shed lots of code, but that you can often massively reduce code size that way. Whether that's the right thing to do is often a fine balance, because it depends a great deal on how many people actually care about the old ways, and sometimes people will get it very wrong in either direction.
Sometimes the 10x more code is actually worth it. But you should be aware when it is 10x more code, and make sure it is worth it.
- pixl97 3y agoRewriting the code isn't the hard part... The QA is the hard part. Developer: "Rewriting this line of code shouldn't change anything" Narrator: It did
- vidarh 3y agoDrastically reducing the codebase if anything tends to make QA a lot easier ;) (though depending on your needs you may or may not like the outcome)