I was a Scala developer for almost ten years and worked on many backend projects. I transitioned from Java after encountering Play Framework Scala examples that appeared cleaner, more expressive, and less verbose. I learned Scala through an EPFL online course, changed jobs to a Scala developer role, and enjoyed interesting projects and talented colleagues. Over time my attitude shifted due to multiple problems in the language ecosystem. The release of Scala 3 and related adaptation issues became the primary trigger for leaving. Additional unspecified problems with the language also contributed to the decision to abandon Scala.
At my first job as a backend engineer, I got a project written in Play Framework. This framework is written in Scala, but you can also use it for Java development. When you read the documentation for Play, it gives you code examples for both Java and Scala, and the Scala code looked much cleaner and expressive. It was free from cumbersome, duplicated Java keywords, and the Scala examples also had fewer lines of code.
I started to learn Scala by completing an online course from Lausanne's tech university (EPFL), where the language originates. Shortly after, I changed jobs, got a position as a Scala developer, and since then, I've worked on many different projects with a Scala backend. I was happy where I was. The projects were interesting and challenging. But more importantly, all the colleagues, the fellow Scala developers, were bright engineers with whom it was a pleasure to work.
Nevertheless, after some years, my attitude to the language has changed. Several problems in the language's ecosystem led me and other developers to abandon Scala. The primary trigger was the release of Scala 3, or to be more concrete, issues related to it. But apart from this, there are also other problems with the language. Scala 3 adaptation issues Scala 3 was released in 2021. It was a long-desired upgrade full of tasty features, and every Scala developer couldn't wait to try them.
Collection
[
|
...
]