[liquidcool]

It is definitely easier to recruit Java/Spring folks. Not only are there way more of them, but there is a lot of competition for Scala folks right now (not just Play, but Spark, etc.), and pretty much any Java EE dev can learn Spring since it's an abstraction. Similarly, I use Groovy/Grails and love it, and can hire Java/Spring people because it's easy for them to learn. With Play, as you know, you throw away all your Java EE knowledge and relearn that stack. You could, of course, hire full stack Java devs and send them to Scala/Play training, assuming you have the time and budget. You might get a lot of folks eager to learn, although they may struggle with functional concepts. Not sure how functional your Scala is.

Is there anything about the app itself that would make either framework more applicable? My hunch is no, but figured I'd ask.

BTW, where are you located? Could affect recruiting.

To me, Angular 2 looks great because of TypeScript, which is so similar to Groovy. Most Java devs seem to prefer it.

[vorg]

> I use Groovy/Grails and love it, and can hire Java/Spring people

Which version of Grails is that? I've heard virtually no-one's upgraded to version 3 since it came out, and not many people are starting new Grails projects, so it's all Grails 2.x. Nowadays, Apache Groovy seems to only be used for glue code, build files, and test scripts.

[dmux]

Sadly tooling support for 3.x isn't as strong as it was/is for the 2.x versions. Trying to get Eclipse or Netbeans to work with Grails 3.x is extremely error prone and buggy.

[bendermoideen]

Thanks !

I have a solution though. The application involves state changes and state management. I am thinking, make the API a simple CRUD layer with Spring Boot, and separate the services that manage the state change. That way I can write them as simple akka actor systems written in Scala, which is where the meat of the application logic lies.