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

Really? I see inheritance as a good antidote for cut'n'paste. If you don't physically duplicate code, you'll never have to read both copies just to make sure they're still the same. I agree most devs do it wrong, but I think it's because they're purely pragmatic and haven't read or thought philosophically about the open/closed principle, programming-by-difference, Liskov-substitutability…

And I do want to remind readers that Moose is not the Perl object system, it's an object system added on top of the mess that a huge collection of legacy code presumes.



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

Search: