Hacker News new | past | comments | ask | show | jobs | submit login

    While deep inheritance hierarchies 
    may seem like a great way of 
    modelling your concepts when you 
    have a blank slate, it’s a 
    recipe for some extremely tight 
    and non-obvious coupling that 
    can deadlock refactoring attempts
    in later phases once those concepts
    have shifted and the original 
    model is no longer a good fit.
This is probably the best critique of nominal inheritance I've read. It really does capture the problem and nicely alludes to the struggle of arguing against an inheritance structure. That it usually starts with many benefits but can easily grow to a constraint.



I kept trying reading this as a haiku.


Ha! Apologies. I gave a somewhat vain attempt at quoting so it would show on phones ok.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: