<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>smaili</author><text>&amp;gt; What irritates me is when people say classes are bad. Or subclassing is bad. Thatʼs totally false. Classes are super important. Reference semantics are super important. If anything, the thing thatʼs wrong is to say, one thing is bad and the other thing is good. These are all different tools in our toolbox, and theyʼre used to solve different kinds of problems.&lt;p&gt;Couldn&amp;#x27;t agree more</text><parent_chain></parent_chain></comment><story><title>Chris Lattner on the Realm WWDC 2017 Swift Panel</title><url>https://oleb.net/blog/2017/06/chris-lattner-wwdc-swift-panel/</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>geodel</author><text>Interesting interview. Java is mentioned many times as language Swift aspires to replace. He is right about Kotlin:&lt;p&gt;&amp;quot;Kotlin is very reference semantics, itʼs a thin layer on top of Java, and so it perpetuates through a lot of the Javaisms in its model.&lt;p&gt;If we had done an analog to that for Objective-C it would be like, everything is an NSObject and itʼs objc_msgSend everywhere, just with parentheses instead of square brackets. ..&amp;quot;&lt;p&gt;I think Swift has real chance to reach Java level popularity. It is already at #11 in Redmonk ranking. All languages above Swift are at least 15 year older than Swift. And once it server side features like concurrency it can be much more general purpose.</text><parent_chain></parent_chain></comment><story><title>Chris Lattner on the Realm WWDC 2017 Swift Panel</title><url>https://oleb.net/blog/2017/06/chris-lattner-wwdc-swift-panel/</url></story>