3 ms·
You can make the same argument about breaking changes. Code is constantly changing and needs to be updated, so breaking backwards compatibility is zero-cost? I
by Shaanie 5y ago
You can make the same argument about breaking changes. Code is constantly changing and needs to be updated, so breaking backwards compatibility is zero-cost?
In reality each change that requires updates to documentation (or code) is of course not actually zero cost.
- shadowgovt 5y agoNot only can you, we often do in the circles I've run in. Adapt or die is the motto out here.
- google234123 5y ago> Adapt or die is the motto out here This is pretty much the view of the left now :p