Now this is just my opinion about Big Corp from experience, I'm all for Scala and have been helping people all over the world with it and Akka. Let me first de

Now this is just my opinion about Big Corp from experience, I'm all for Scala and have been helping people all over the world with it and Akka. Let me first define Big Corp. A traditionally long standing business (good ole boys) type of company. A financial or insurance institution, with hundreds of employees in I.T., devs, QA, and deployment. I've seen big corps with large teams who are entrenched in .Net or Java mention they also must worry about getting people to understand your Scala code. Hate to say it, but I've meet a lot of supposed Java programmers who didn't know what a HashMap was... in big corp... In my experience, they just (big corp) don't give a crap. It's Java or .Net and if you don't like it... leave. Unless that one small group going rouge and using Scala has full backing from the top you'll find yourself on a deserted island in time... which doesn't mean to say that they won't give you a shot. They will but they want 2-3x results. Otherwise why break what you have now? I'm just saying that is what I see them thinking. I believe it has to do more with the type of project and if it has real visible impact on the bottom line to whether Scala or X,Y,Z will succeed in the big corp env. Project A does well, makes Big Corp more $$$ then they try to reproduce. Mr. VP of finance doesn't care if it's Scala or Alacs (Scala backwards) and that Scala helps you write less code. Small Corp might though as they have less resources (funds/time). Just my opinion from interfacing with Big Corp. I did leave (each one) after I got tired of trying to champion better ways of doing things.