<story><title>Why you might want to choose Ceylon</title><url>http://ceylon-lang.org/blog/2015/10/27/why/</url></story><parent_chain><item><author>lmm</author><text>Have they tightened up the floating point semantics? Or do you still get different rounding behaviour on the JVM, dart and JS?&lt;p&gt;I want to like Ceylon because it&amp;#x27;s the language Scala should be (assuming that higher-kinded types made it in - I could never work without them). It&amp;#x27;s Scala with all the ugly parts polished away, Scala with ten years&amp;#x27; progress in language design.&lt;p&gt;But it does nothing that Scala can&amp;#x27;t. Scala might need a pile of bodges to offer these things - Shapeless implicit macros to use tuples generically, type-level libraries abusing the implicit resolution rules to implement unions, a retrofitted JavaScript backend. But that stuff has been written now, and as a developer it works - maybe with a couple of ugly extra lines here and there, but that&amp;#x27;s all.&lt;p&gt;I&amp;#x27;m glad it exists, but I just can&amp;#x27;t see people choosing the more polished language over the one with ten years worth of library and tool support when there&amp;#x27;s no USP beyond that polish.</text></item></parent_chain><comment><author>lukedegruchy</author><text>Experimental support for higher order generics will be in 1.2 (JavaScript runtime only):&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;ceylon-lang.org&amp;#x2F;blog&amp;#x2F;2015&amp;#x2F;06&amp;#x2F;03&amp;#x2F;generic-function-refs&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;ceylon-lang.org&amp;#x2F;blog&amp;#x2F;2015&amp;#x2F;06&amp;#x2F;03&amp;#x2F;generic-function-refs...&lt;/a&gt;
&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;ceylon-lang.org&amp;#x2F;blog&amp;#x2F;2015&amp;#x2F;06&amp;#x2F;12&amp;#x2F;more-type-functions&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;ceylon-lang.org&amp;#x2F;blog&amp;#x2F;2015&amp;#x2F;06&amp;#x2F;12&amp;#x2F;more-type-functions&amp;#x2F;&lt;/a&gt;</text></comment>
<story><title>Why you might want to choose Ceylon</title><url>http://ceylon-lang.org/blog/2015/10/27/why/</url></story><parent_chain><item><author>lmm</author><text>Have they tightened up the floating point semantics? Or do you still get different rounding behaviour on the JVM, dart and JS?&lt;p&gt;I want to like Ceylon because it&amp;#x27;s the language Scala should be (assuming that higher-kinded types made it in - I could never work without them). It&amp;#x27;s Scala with all the ugly parts polished away, Scala with ten years&amp;#x27; progress in language design.&lt;p&gt;But it does nothing that Scala can&amp;#x27;t. Scala might need a pile of bodges to offer these things - Shapeless implicit macros to use tuples generically, type-level libraries abusing the implicit resolution rules to implement unions, a retrofitted JavaScript backend. But that stuff has been written now, and as a developer it works - maybe with a couple of ugly extra lines here and there, but that&amp;#x27;s all.&lt;p&gt;I&amp;#x27;m glad it exists, but I just can&amp;#x27;t see people choosing the more polished language over the one with ten years worth of library and tool support when there&amp;#x27;s no USP beyond that polish.</text></item></parent_chain><comment><author>taiar</author><text>&amp;gt; I want to like Ceylon because it&amp;#x27;s the language Scala should be&lt;p&gt;&amp;gt; but I just can&amp;#x27;t see people choosing the more polished language over the one with ten years worth of library and tool support when there&amp;#x27;s no USP beyond that polish&lt;p&gt;It seems all a matter of time. What would Ceylon look like to you after some years of library and tool support?</text></comment>