That's an old article. Scala's now on 2.9.2 and soon to be 2.10, binary compatibility is being taken very seriously.
The migration manager is now open source, and available as a plugin for SBT: http://blog.typesafe.com/migration-manager-for-scala-is-now-open-sourc Compatibility has now become sufficiently trusted that projects are beginning to drop the scala version identifier from their maven artefact names (akka and spray are the first two that spring to mind) Trust me, the industry *do* care. All except for those parts of it who see IT as an unfortunate cost centre, and wish it could just have been locked permanently at COBOL so they'd avoid all those awkward programmer salaries. I'm hoping that the vast majority of people on this list appreciate the futility of such an attitude. On 20 July 2012 00:41, Josh Berry <[email protected]> wrote: > On Thu, Jul 19, 2012 at 5:58 PM, Kevin Wright <[email protected]> > wrote: > > Case in point... Sun/Oracle took too long to add modules so they could > > remove deprecated code from Java, they've been suffering from postponed > or > > feature-limited releases as a result. > > I question how much they are "suffering" from this. There is a vocal > minority that wants it, to be sure. The industry, by and large, seems > to not care. > > > Once you have modules, it becomes far easier to release everything else > in a > > perfectly useable but less than 100% complete condition, because you then > > have the scope to revert design choices in a subsequent version. > > This really only works if you don't have entire industries that depend > on your current design remaining. Pollack's critique of Scala's > system for being ridiculously fragile would be a pale candle compared > to the flame that you seem to be describing. > > > http://lift.la/scalas-version-fragility-make-the-enterprise > > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
