Hacker News Reader

Comment by donjigweed | Hacker News Reader

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.

View on HN

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.

And your organization has much more than 3 teams? The article specifically says this is a large multi-team coordination issue.

noelwelsh is responding to donjigweed, not the article.

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.

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.

Zero. The 2.8 to 2.9 upgrade took exactly one extra build cycle, which we had already committed other code to test anyways.

I spent zero time on it. And I regularly run my code against 2.9 and 2.10 trunk. No problems so far.

Reply on news.ycombinator.com