<story><title>Kotlin/Native Tech Preview: Kotlin without a VM</title><url>https://blog.jetbrains.com/kotlin/2017/04/kotlinnative-tech-preview-kotlin-without-a-vm/</url></story><parent_chain><item><author>saosebastiao</author><text>I&amp;#x27;m skeptical of the strategic advantage of being backed by a tooling company, because of the fact that tooling is often a preference that comes with holy wars attached. If Emacs sponsored a language, how many Vim users would jump ship? I know plenty of Java devs that actually prefer Eclipse (WTF?!?!?). Good luck getting an entire team onboard with a single IDE.&lt;p&gt;Throw in the fact that their IDE software is open source only until you need the most advanced features, and I can imagine Kotlin never picking up as much steam as Rust or Swift with their comparably inferior tooling ecosystems. I can imagine C# taking over java before Kotlin does.</text></item><item><author>jorgemf</author><text>kotlin is backed by a tooling company. This is a very strong argument. The ones that are doing the best IDE for java (for a lot of people) are the ones that decided to create kotlin. Swift also has the tooling support of Apple, but I only read complains about tooling around Swift. Go and Rust are very niche compare to java or swift, while kotlin can replace java completely and now it is aiming for native backend projects.</text></item><item><author>geodel</author><text>May they all do great. But I am sceptical that Scala&amp;#x2F;Kotlin and many others started in last decade stand chance against Java&amp;#x2F;Rust&amp;#x2F;Swift&amp;#x2F;Go. IMO these 4 are backed by powerful corporations and have large community momentum. They are going to keep &amp;gt;90% of all software work along with C&amp;#x2F;C++.</text></item><item><author>virtualwhys</author><text>&amp;gt; This Technology Preview features automatic reference counting with a cycle collector on top, but what the final memory management solution(s) will look like is unknown at this point.&lt;p&gt;Same issue with Scala Native[1]. Both projects are a long way from being production ready wrt to targeting ios, android and desktop.&lt;p&gt;Probably at least a couple of years before either project delivers the one-language-to-rule-them-all.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;scala-native&amp;#x2F;scala-native&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;scala-native&amp;#x2F;scala-native&lt;/a&gt;</text></item></parent_chain><comment><author>fasquoika</author><text>&amp;gt;If Emacs sponsored a language&lt;p&gt;Emacs does sponsor a language (elisp), and it&amp;#x27;s most people&amp;#x27;s reason for using it.</text></comment>
<story><title>Kotlin/Native Tech Preview: Kotlin without a VM</title><url>https://blog.jetbrains.com/kotlin/2017/04/kotlinnative-tech-preview-kotlin-without-a-vm/</url></story><parent_chain><item><author>saosebastiao</author><text>I&amp;#x27;m skeptical of the strategic advantage of being backed by a tooling company, because of the fact that tooling is often a preference that comes with holy wars attached. If Emacs sponsored a language, how many Vim users would jump ship? I know plenty of Java devs that actually prefer Eclipse (WTF?!?!?). Good luck getting an entire team onboard with a single IDE.&lt;p&gt;Throw in the fact that their IDE software is open source only until you need the most advanced features, and I can imagine Kotlin never picking up as much steam as Rust or Swift with their comparably inferior tooling ecosystems. I can imagine C# taking over java before Kotlin does.</text></item><item><author>jorgemf</author><text>kotlin is backed by a tooling company. This is a very strong argument. The ones that are doing the best IDE for java (for a lot of people) are the ones that decided to create kotlin. Swift also has the tooling support of Apple, but I only read complains about tooling around Swift. Go and Rust are very niche compare to java or swift, while kotlin can replace java completely and now it is aiming for native backend projects.</text></item><item><author>geodel</author><text>May they all do great. But I am sceptical that Scala&amp;#x2F;Kotlin and many others started in last decade stand chance against Java&amp;#x2F;Rust&amp;#x2F;Swift&amp;#x2F;Go. IMO these 4 are backed by powerful corporations and have large community momentum. They are going to keep &amp;gt;90% of all software work along with C&amp;#x2F;C++.</text></item><item><author>virtualwhys</author><text>&amp;gt; This Technology Preview features automatic reference counting with a cycle collector on top, but what the final memory management solution(s) will look like is unknown at this point.&lt;p&gt;Same issue with Scala Native[1]. Both projects are a long way from being production ready wrt to targeting ios, android and desktop.&lt;p&gt;Probably at least a couple of years before either project delivers the one-language-to-rule-them-all.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;scala-native&amp;#x2F;scala-native&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;scala-native&amp;#x2F;scala-native&lt;/a&gt;</text></item></parent_chain><comment><author>true_religion</author><text>&amp;gt; Good luck getting an entire team onboard with a single IDE.&lt;p&gt;Many companies mandate that you use Visual Studio to develop with because their entire toolchain is setup to build the project via VS tools. Deviating from that means that no one can help you, and you&amp;#x27;re probably polluting the repo with your own ad-hoc tooling.</text></comment>