Scala complexity issues
Firstly, this thread [meaning this one ] seems too pessimistic to me. Scala is used in a huge and growing number of commercial companies, many of which employ more than 100 developers. All these people just do their job (and mostly love it); they do not find the complexity of Scala too frightening.
Secondly, I’m sure we’ve come to understand that complexity and power are quite balanced in Scala. Remove some of the complexity and lose some of the power. Here, by power, I mean "The number of concepts that you can express in language with absolute precision." I want to get away from the commonly used argument that all Turing-full languages ​​are ultimately equally powerful.
Thirdly, if you look at other languages, they always have a certain set of “best practices” that are distributed with them and are used as directions to action. This culture of good practice changes over time, as demonstrated by the evolution of JEE. Since Scala for business is still young, our practices are still evolving and stabilizing.
And this is your chance! If you create good libraries with simple APIs, you have a great chance to influence future best practices in Scala while they are still in the making. I would like us to concentrate on these points and not on twisting our own hands.
')
Can these practices be created under the influence of tools like “style checkers”? Maybe. We definitely want to develop them. But to entrust the responsibility for creating good practices exclusively to tools will be stupid.
[UPD corrected typos and Russified the text a little more]
Secondly, I’m sure we’ve come to understand that complexity and power are quite balanced in Scala. Remove some of the complexity and lose some of the power. Here, by power, I mean "The number of concepts that you can express in language with absolute precision." I want to get away from the commonly used argument that all Turing-full languages ​​are ultimately equally powerful.
Thirdly, if you look at other languages, they always have a certain set of “best practices” that are distributed with them and are used as directions to action. This culture of good practice changes over time, as demonstrated by the evolution of JEE. Since Scala for business is still young, our practices are still evolving and stabilizing.
And this is your chance! If you create good libraries with simple APIs, you have a great chance to influence future best practices in Scala while they are still in the making. I would like us to concentrate on these points and not on twisting our own hands.
')
Can these practices be created under the influence of tools like “style checkers”? Maybe. We definitely want to develop them. But to entrust the responsibility for creating good practices exclusively to tools will be stupid.
[UPD corrected typos and Russified the text a little more]
Source: https://habr.com/ru/post/133347/
All Articles