Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Then the same would be the case for code duplication which really ought to be unified.


I don't think I agree. Identifying an abstraction as leaky and breaking it apart is substantially more difficult and riskier than identifying duplication and creating an abstraction for it.


Removing an abstraction layer can usually be done mechanically by inlining the calls. This is a trivial operation. Identifying duplication not trivial since there might be various differences and you have to investigate if they are inconsequential or not.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: