Does it make sense to transfer a java project to scala?

Question

Java

Good evening!
Actually there is a project in java:
- hibernate
- jsf
- a bunch of js libraries
- tomcat
Does it make sense to move to scala (at the first stage, the model + controllers will be described on the scala, giving content to ajax requests from all jquery ui components wound over jsf). And how hard would it be to do? I think there is something like scala sdk that needs to be added to cp so that all this economy generally works in jvm. Or I'm wrong. In general, this idea does not come from me and I need to understand whether it is worth venturing at all.

Answer 1

Are you missing something in java, or do you just want 'technology for technology's sake'? It seems to me that the answer is obvious if you figure out what you are missing in java? can you do without it? what are the real benefits I get from using scala? Or will it be used because it's fashionable? First of all, look at the problem being solved, and not fashionable technologies. If the technology helps to solve the problem - it makes sense to use it, otherwise - no.

Answer 2

net

Answer 3

There is enough for Java, maybe sometimes you want dynamic typing, but this is not critical. I myself do not really favor the rock, I perceive it as undead, but I liked lisp at one time)) But young people want something new, and they are aggressive, they break through)) So I want to understand what can be raked from such a move. Groovy, for example, went into the project well, but it is only for specific purposes, it’s more pleasant to write liquidbase migrations on it, it’s nice to run the groovy console and torture model objects in it, it’s nice to use metaprogramming sometimes. What about the rock? Will she also be able to quietly lie down in the project or will she pull a bunch of all sorts of g there?

Answer 4

The question requires clarification, what exactly do you want to port to Scala?
- Part of the logic
- Complete rejection of Java
- Rewrite everything in Scala from 0