<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>FlyingSnake</author><text>One big potential pitfall people seldom discuss is that Java is moving in a different direction and taking JVM along with it. This will cause problems in the future for Kotlin in areas such as reification and nullability.</text><parent_chain><item><author>robertjpayne</author><text>Kotlin running on the JVM is a disadvantage outside of Android though in a lot of spaces. Rust&amp;#x2F;Swift&amp;#x2F;Go will use a fraction of the ram to run a server application than Kotlin will.</text></item><item><author>fzeindl</author><text>Kotlin is a much more likely candidate. Excellent IDE support, deep integration with Java, already the go-to language for Android, many years of production and less &amp;quot;different&amp;quot; than Rust.</text></item><item><author>K0nserv</author><text>I&amp;#x27;m quite bullish on this method of cross-platform i.e. a common shared core leveraging native UI toolkits. Every incarnation of cross-platform on the market today sits somewhere between mediocre and bad in terms of the resulting UX. This approach strikes a good balance between sharing code and being platform native I think. Swift is a good contender for doing this and so is, I think, Rust.</text></item></parent_chain></comment><story><title>Interoperability: Swift’s Super Power</title><url>https://browsercompany.substack.com/cp/137231709</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>jwells89</author><text>Also, it brings various Java baggage along for the ride, which isn’t everybody’s cup of tea.&lt;p&gt;And while it’s syntactically similar to Swift, I find it to be overall less ergonomic in various ways.</text><parent_chain><item><author>robertjpayne</author><text>Kotlin running on the JVM is a disadvantage outside of Android though in a lot of spaces. Rust&amp;#x2F;Swift&amp;#x2F;Go will use a fraction of the ram to run a server application than Kotlin will.</text></item><item><author>fzeindl</author><text>Kotlin is a much more likely candidate. Excellent IDE support, deep integration with Java, already the go-to language for Android, many years of production and less &amp;quot;different&amp;quot; than Rust.</text></item><item><author>K0nserv</author><text>I&amp;#x27;m quite bullish on this method of cross-platform i.e. a common shared core leveraging native UI toolkits. Every incarnation of cross-platform on the market today sits somewhere between mediocre and bad in terms of the resulting UX. This approach strikes a good balance between sharing code and being platform native I think. Swift is a good contender for doing this and so is, I think, Rust.</text></item></parent_chain></comment><story><title>Interoperability: Swift’s Super Power</title><url>https://browsercompany.substack.com/cp/137231709</url></story>