News for hackers. Stuff that matters.
Re:Scala's version fragility makes the enterprise argument n... by donjigweed on Wednesday December 07, 2011 @02:57PM (#3325612)
Really, it is just becoming increasingly difficult to see how proponents of Scala can credibly claim any kind of developer productivity gains. I can only imagine how much time your average Scala developer spends solving problems of accidental complexity that simply do not exist in more mature languages.
Re:Scala's version fragility makes the enterprise argument n... by noelwelsh on Wednesday December 07, 2011 @03:10PM (#3325695)
As a Scala developer, let me shed some light on this. In the last few months I have spent exactly zero time on this problem. It was a minor issue when 2.9 came out. No one forces you to upgrade, and we didn't till all our dependencies worked on 2.9.
Re:Scala's version fragility makes the enterprise argument n... by rickmode on Wednesday December 07, 2011 @03:30PM (#3325829)
And your organization has much more than 3 teams? The article specifically says this is a large multi-team coordination issue.
Re:Scala's version fragility makes the enterprise argument n... by lliiffee on Wednesday December 07, 2011 @06:21PM (#3326690)
noelwelsh is responding to donjigweed, not the article.
Re:Scala's version fragility makes the enterprise argument n... by SWengineer on Wednesday December 07, 2011 @03:22PM (#3325773)
Time spent: zilch, perhaps because most of my dependencies are java libs not scala ones. Like many Java devs starting out using Scala as a 'better java' which means adding more scala libs over time. It's definitely very pleasant to code in Scala vs Java, def more productive, to a surprising extent even. The compatibility issue needs to be addressed though.
Re:Scala's version fragility makes the enterprise argument n... by brightsize on Wednesday December 07, 2011 @04:16PM (#3326063)
Same here, zero time spent on this. Scala is a joy to program in. It's good to see these kinds of postings with complaints and suggestions. They'll move the language and the ecosystem forward.
Re:Scala's version fragility makes the enterprise argument n... by mark242 on Wednesday December 07, 2011 @10:26PM (#3327443)
Zero. The 2.8 to 2.9 upgrade took exactly one extra build cycle, which we had already committed other code to test anyways.
Re:Scala's version fragility makes the enterprise argument n... by soc88 on Wednesday December 07, 2011 @06:44PM (#3326767)
I spent zero time on it. And I regularly run my code against 2.9 and 2.10 trunk. No problems so far.