Should we go Scala instead of Java? [closed]

As it currently stands, this question is not a good fit for our Q开发者_Python百科&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 11 years ago.

We will be starting a new project which will involve training all the .net developers in Java (frameworks/ECO system etc). We have a lot of code written in C# and it seems that all of this will be wasted as we have to re-write it all in Java. The problem I see is that the first year or so (probably 2 years) we will have nothing to deliver as we will spend most of the time reproducing what we had before but now in Java.

Since our team is distributed in different offices around the world and we have a large number of java developers (20 to 30) and 10 developers using .net, we want to get all the developers using the same language/platform so we can start to reuse components/modules. So I can understand managements point of view.

Yesterday I came across Scala and was wondering if it would be better to use this with the current product (which is written in C#) and then at least we will have a working product in a year. Also in a year we have modules that can be used in the Java world whilst we migrate other parts of the product.

Would this work?

JD

---

David Pollak wrote a couple of blog posts about this very recently. His opinion was very clear that your team would be a very poor choice for Scala.

http://www.javacodegeeks.com/2011/09/yes-virginia-scala-is-hard.html

http://www.javacodegeeks.com/2011/09/scala-use-is-less-good-than-java-use.html