<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>zozbot234</author><text>&amp;quot;Tightly binding data and code&amp;quot; allows you to maintain complex invariants via code, and to abstract away from the specifics of any single implementation. Statefulness per se is quite manageable; what&amp;#x27;s not manageable is &lt;i&gt;shared, mutable&lt;/i&gt; state that isn&amp;#x27;t isolated to a single, modular, highly cohesive &amp;quot;unit&amp;quot; of code that can be understood in its totality.  The real issues with OOP have to do precisely with things that &lt;i&gt;break&lt;/i&gt; these principles, viz. implementation inheritance.</text><parent_chain><item><author>lgessler</author><text>This doesn&amp;#x27;t speak to what I consider some of the most dangerous parts of OOP, which include the assumptions that tightly binding data and code is helpful, and that statefulness is fine to freely sprinkle throughout your program.</text></item></parent_chain></comment><story><title>The Case Against OOP Is Wildly Overstated</title><url>https://medium.com/young-coder/the-case-against-oop-is-wildly-overstated-572eae5ab495</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>lkrubner</author><text>I was about to write exactly this. In 2014 I wrote an essay that has been discussed here on Hacker News several times [1]. When I re-read it now, parts of it seem very subtle, parts of it seem to be matters of opinion, but what jumps out is how really dangerous it is to tightly bind data with behavior, especially because this then leads to the problem of initiation (which I devote a lot of time to talking about in the essay).&lt;p&gt;[1] Object Oriented Programming Is An Expensive Disaster Which Must End&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.smashcompany.com&amp;#x2F;technology&amp;#x2F;object-oriented-programming-is-an-expensive-disaster-which-must-end&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.smashcompany.com&amp;#x2F;technology&amp;#x2F;object-oriented-progr...&lt;/a&gt;</text><parent_chain><item><author>lgessler</author><text>This doesn&amp;#x27;t speak to what I consider some of the most dangerous parts of OOP, which include the assumptions that tightly binding data and code is helpful, and that statefulness is fine to freely sprinkle throughout your program.</text></item></parent_chain></comment><story><title>The Case Against OOP Is Wildly Overstated</title><url>https://medium.com/young-coder/the-case-against-oop-is-wildly-overstated-572eae5ab495</url></story>