| I still have the problem of upgrading because not all of the libraries are cross compile or do work. At the end of last year we've upgraded one library which cost us many days. Next is upgrading Lift to 3.0 which will be a nightmare (again). "We've also invested heavily in incremental compilation in sbt." Yes, I read this over and over again, and I see micro benchmarks posted. Using SBT with continuous unit testing I can't feel a difference - or it is so slow with a major code base that it's still much to slow and I judge it having no progress. Either way, after years it is still too slow (newest Scala + newest SBT). "I rarely have time for office chair sword fights anymore." Today I expect Kotlins practically instant compilation. 10 seconds for compiling some changed files is already to much for rapid development with TDD/Web, it breaks my flow, but YMMV. "We'll have some graphs to show you soon," See above, I've seen dozens of micro benchmarks that claim improvements, in the end it doesn't show up in my real projects - at least in mine and the person who migrated to Go in the linked article. And all the other blog post authors that moved away from Scala towards something faster (Kotlin, Java 8, Go, ...) But as I've said, I've moved on to Kotlin for new projects because for me Scala is a lost course. |