Scala project - what are the difficulties of maintaining the code over time?

Question

Scala

Hello.
The programmer convinces to do the project in Scala.
Allegedly, tasks are solved more simply and quickly.
But in many articles about Scala they write that it is difficult to support projects in this language.
Please help me to understand what exactly is the problem?
And also, how much is the right decision - to do a new project in Scala.
Thanks

Answer 1

Perhaps "many articles" mean that Scala is a very flexible multi-paradigm language in which the same functionality can be written in dozens of ways. If a project needs to be supported for many years and by dozens or more developers, then each developer hired will either have to be retrained, or the code will quickly turn into a hodgepodge of styles and approaches that is difficult to understand.

Answer 2

You need to provide the solution of technical issues to the technical specialists who will be involved in the implementation.
it is easier to maintain what is more understandable to you , and more understandable things are just familiar things.
You need to understand who will support the project (Scala is not as common as JS, for example), if you need to find 1-2 smart people to support, you can do it in any language (including scala).
If you need hundreds of people to recruit - you will certainly find yourself a hundred rock climbers. Although you probably won’t find a hundred sensible JS nicknames either))))
If the project is supported by the same developer (then you need to let him choose a more convenient tool on his own)
-------
again, the typical practice now is to pack part of the functionality into a microservice and generally don’t go there, develop different microservices using technologies that are convenient for developers.
the typical lifetime of such a microservice is 3-5 years, then it is often thrown out / replaced altogether.

Answer 3

Most likely, it will be quite difficult to find a Scala programmer, if the current one leaves, and the project needs to be supported and developed.
It's not the most important argument, perhaps, but in many cases it's important enough. And most likely, any Scala programmer will want more money.