tag:blogger.com,1999:blog-5797202.post7903684839431534885..comments2023-04-29T17:39:44.808+02:00Comments on Random thoughts by Ceki Gülcü: Is Scala worthy of your trust?Unknownnoreply@blogger.comBlogger10125tag:blogger.com,1999:blog-5797202.post-72188454301693144942011-12-16T10:00:07.812+01:002011-12-16T10:00:07.812+01:00Very interesting reading
http://gridgaintech.word...Very interesting reading<br /><br />http://gridgaintech.wordpress.com/2011/12/11/offbeat-scala-by-the-end-of-2011-no-drama-but-frustration-is-growing/<br /><br />http://blog.frankel.ch/java-scala-complexity-and-aardvarks<br /><br />http://blog.joda.org/2011/11/scala-feels-like-ejb-2-and-other.html<br /><br />http://blog.joda.org/2011/11/scala-ejb-2-feedback.htmlAnonymoushttps://www.blogger.com/profile/01689164934810739741noreply@blogger.comtag:blogger.com,1999:blog-5797202.post-25259131507468165542011-10-23T18:31:12.997+02:002011-10-23T18:31:12.997+02:00I also think that setting a higher priority for pr...I also think that setting a higher priority for preserving compatibility is the key here. If Scala users ask for it respectfully and in numbers, it is more likely to happen.Cekihttps://www.blogger.com/profile/06948108407442025539noreply@blogger.comtag:blogger.com,1999:blog-5797202.post-58554239694513296472011-10-22T10:15:59.340+02:002011-10-22T10:15:59.340+02:00I've been complaining about this for years – h...I've been complaining about this for years – here's my tale on it two years ago:<br /><br />http://alblue.bandlem.com/2009/10/scala-is-still-not-enterprise-ready.html<br /><br />Unfortunately whilst Scala still holds out hope, in reality it had little chance of succeeding in the long term because systems written in Scala essentially become unmaintainable. <br /><br />In the days of C, andAlBluehttps://www.blogger.com/profile/06362201865553416948noreply@blogger.comtag:blogger.com,1999:blog-5797202.post-3512194594921574792011-10-15T10:26:56.028+02:002011-10-15T10:26:56.028+02:00Hello different Steve,
The case you describe sound...Hello different Steve,<br />The case you describe sounds like a momentary window of breakage rather than a long term structural failure.<br /><br />Presumably Scala 2.9.2 will be released shortly and you will be able to use packages compiles against 2.9.x without problems.Cekihttps://www.blogger.com/profile/06948108407442025539noreply@blogger.comtag:blogger.com,1999:blog-5797202.post-57090979715817519472011-10-14T20:44:34.913+02:002011-10-14T20:44:34.913+02:00(Different Steve here...)
If the Scala update was...(Different Steve here...)<br /><br /><i>If the Scala update was triggered by an IDE update, reverting to the older version of Scala may be particularly painful. If removing the non-compliant dependency is impossible, you will be hung out to dry.</i><br /><br />This reminded me of my painful attempt to use the latest Scala Eclipse plugin, which mysteriously required the not-yet final Scala 2.9.2 Stevenhttps://www.blogger.com/profile/02546246502778693980noreply@blogger.comtag:blogger.com,1999:blog-5797202.post-65900331734176866722011-08-27T12:53:24.917+02:002011-08-27T12:53:24.917+02:00Not really. Just look at the breakage which occurr...Not really. Just look at the breakage which occurred during the migration at that time. Add the changes to the memory model, to threading, ...<br />Considering that most packages are exempted from any compatibility guarantees in Java SE and the changes to javax, Swing and AWT, deprecation of JVMDI and JVMPI, breakages due to Classloader, compiler changes, assertion facilities, Generics and dozen stevehttps://www.blogger.com/profile/03224058522791620723noreply@blogger.comtag:blogger.com,1999:blog-5797202.post-65428861349177416912011-08-26T19:44:32.106+02:002011-08-26T19:44:32.106+02:00FYI, code compiled against java 1.1 will run under...FYI, code compiled against java 1.1 will run under Java version 1.1 and any subsequent version of Java. More generally, code compiled against Java version N will run perfectly under version N and any subsequent version of Java.<br /><br />In the Scala world, the same does not hold true. Code compiled against Scala 2.7 will not run under subsequent versions such as 2.8 or 2.9. This limitation is Cekihttps://www.blogger.com/profile/06948108407442025539noreply@blogger.comtag:blogger.com,1999:blog-5797202.post-74940959934830136012011-08-26T19:04:27.912+02:002011-08-26T19:04:27.912+02:001) No, of course not. ^^
2) Care to tell me where...1) No, of course not. ^^<br /><br />2) Care to tell me where I'm mistaken?stevehttps://www.blogger.com/profile/03224058522791620723noreply@blogger.comtag:blogger.com,1999:blog-5797202.post-71048844436862032872011-08-26T15:11:11.912+02:002011-08-26T15:11:11.912+02:00Steve,
1) Are you real?
2) If you are real, the...Steve, <br /><br />1) Are you real?<br /><br />2) If you are real, then you are just going to alienate people with your attitude.Cekihttps://www.blogger.com/profile/06948108407442025539noreply@blogger.comtag:blogger.com,1999:blog-5797202.post-66051364444139857812011-08-26T14:15:39.151+02:002011-08-26T14:15:39.151+02:00Mhhh. Looks like you missed the whole last year.
...Mhhh. Looks like you missed the whole last year.<br /><br /> - The binary changes between 2.x releases are exactly as specified. Binary compatibility is only a concern between 2.x.y releases. The x-part of the version number is like the Java X, where also binary incompatible changes appear.<br /><br /> - The tools for detecting breakage already exist.<br /><br /> - Language level primitives are stevehttps://www.blogger.com/profile/03224058522791620723noreply@blogger.com