note
FoxtrotUniform
<blockquote>
Anyhow, OO is fine -- but don't think it's about reuse or maintainability or massive inheritance hierachies or anything like that. It's mostly about state and clean interfaces -- or, at least -- that's how it SHOULD be. The number of real world problems correctly modelled by massive inheritance trees are few and far between.
</blockquote>
<p>If you ask me, OO is a method for modelling problems that are based on interactions between Things. Not all problems are easily or properly modelled this way. When used for suitable problems, object-oriented code can be stunningly elegant; when used for unsuitable problems, it's usually a steaming heap of <strike>crap</strike> unnecessary complexity.</p>
<p>[tilly] argued this point better and more completely: [The world is not object oriented].</p>
<div class="pmsig"><div class="pmsig-95145">
<p><tt>-- </tt><br>
Yours in pedantry,<tt><br>
<font color="#330000">F</font>
<font color="#550000">o</font>
<font color="#770000">x</font>
<font color="#990000">t</font>
<font color="#bb0000">r</font>
<font color="#dd0000">o</font>
<font color="#ff0000">t</font>
<font color="#ff0000">U</font>
<font color="#dd0000">n</font>
<font color="#bb0000">i</font>
<font color="#990000">f</font>
<font color="#770000">o</font>
<font color="#550000">r</font>
<font color="#330000">m</font>
</tt><br>
[id://399880|"Lines of code don't matter as long as I'm not writing them."] -- [merlyn]</p>
</div></div>
401489
402266