Scala 3 Migration: Report from the field

Scala used to be my hobby &#x2F; enthusiast language. Introduced to it through a college course, and used a bit through school. Later, I would use it for Advent of Code, tinkered with a Scala Play webapp, and dream about using it professionally. Rust has almost completely filled that void now. Rust is native, I&#x27;m not waiting on the 1.0 release of `scala-native` anymore. The community around Rust seems to be enthusiastic and growing, as opposed to languishing for Scala. I hold some reservations about Rust in terms of how complicated it is. Despite having used it for an amount of time that I would be feeling comfortable in most languages, I am still not comfortable and continually encounter _stuff I don&#x27;t understand_.<p>RIP Scala, I will miss you! You showed me the joy of pattern matching, functional OO, currying, how to use `map` `flatMap` `fold`, etc. All things with continued influence! &lt;3

I left the Scala ecosystems (mostly) a year or 4 ago, right around the release of Scala 3. It&#x27;s a shame that the compatibility and tooling situation doesn&#x27;t seem to have improved much since then. The Scala devs always said they wanted to avoid a Python 2-&gt;3 situation, but it seemed like they didn&#x27;t quite achieve that.

Back when I used to use Scala, the biggest PITA was how every minor version bump you&#x27;d run into binary version incompatibilities that you&#x27;d only run into at runtime. Has that situation changed?<p>I&#x27;ve always felt that Scala the language was always pretty nice, but Scala the ecosystem&#x2F;tooling was moderately painful to work with. It was getting better over time, but they lost all the momentum they had.

That&#x27;s how I learned to do migrations&#x2F;major refactoring from my mentors back in the days.<p>First brute force it, observe but don&#x27;t panic, until you don&#x27;t get any further.<p>Then start over and do it properly.

This is a good report. I started a project last year on Scala 2.13, but had all Scala 3 compatibility features&#x2F;warnings enabled from the beginning. It sounds like it should be an easy upgrade in the future as long as I don&#x27;t rely on macros or libraries that rely on macros. I&#x27;ve tried to stick to libraries that already have Scala 3 releases or that come from plain Java.

This is a good report.<p>Scala 3 is really what Scala was supposed to be. The language is just about perfect, and the most important and popular libraries and tools (Cats&#x2F;Cats Effect, ZIO, Play Framework, Akka&#x2F;Apache Pekko) are all supporting the new version for years already.<p>It&#x27;s really a shame that IDE support has yet to catch up and the dev experience is frustrating at times, but I&#x27;m using Scala 3 for everything I can.

I only allow myself to use Scala these days if follow some rules: no sbt (just Maven) and no Scala libraries (just Java ones). I never used fancy stuff like Cats anyways. Curious to hear who actually does, and for what.

I currently work at a company who is primarily writing in Scala. I really like Scala but assume my next role won’t be in that. Are my two best options Rust and Java if I want to keep some of the typing, functional style, and pattern matching while also moving to a more popular language?

It will be interesting to see how Clojure and Scala do in the longer run in the industry oriented FP languages scene. I wonder if there&#x27;s any data points around that could tell a tale.

Migrated a Scala 2.8(!) era codebase to Scala 3.<p>As OP explains, macros and abstract type projections tend to be the biggest pain points in complex applications; otherwise, with Scala Rewrite tool it&#x27;s pretty straightforward.<p>I think it&#x27;s more inertia than anything else that more Scala 2 companies don&#x27;t migrate.<p>Unpopular opinion, but setting a Scala 2 sunset time would spur companies into action :)<p>As it stands Akka (previously Lightbend, previously TypeSafe) is the maintainer of Scala 2, and derives part of its revenue from Scala 2 support contracts so there&#x27;s even less incentive to migrate when there&#x27;s no EOL date as Python 2 (eventually) had.

This is a great write up! For people using gradle to compile scala (definitely not my first choice) the initial hurdle to migrating individual modules has been fixed! I&#x27;m guessing it&#x27;ll be in gradle 8.13 <a href="https:&#x2F;&#x2F;github.com&#x2F;gradle&#x2F;gradle&#x2F;pull&#x2F;31118">https:&#x2F;&#x2F;github.com&#x2F;gradle&#x2F;gradle&#x2F;pull&#x2F;31118</a>

I didn&#x27;t know the ecosystem wasn&#x27;t on 3.<p>It was released May 2021.<p>It is a big change though.

Currently work on a Scala&#x2F;Spark project as part of our work. Everyone hates it except the one guy who knows it well, but for most people who spend most of their time doing imperative languages its just too much of a mind jump. Hopefully soon we&#x27;ll be on a new big data platform soon and we wont have to deal with a migration like this.

As I mentioned deeper in the thread, <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=42969519">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=42969519</a>, Java seems to have caught up with Kotlin and Scala language wise. (With Scala3 having the most extensive type system.)<p>The ecosystem also seems to have petered out. Akka, spark, and flink used to be reasons to do scala. But they have decent java interfaces now.<p>I’ve had too much struggles convincing colleagues that actually more information in the type is convenient. It seems like the same religion of untyped vs typed.<p>What is left as reasons to choose for scala or Kotlin?

I am wondering whether with GenAI, migrations like this one will be less and less painful, and therefore more people will be able to migrate to newer technologies&#x2F;versions sooner and quicker.

Scala has some nice and cool vibes and features to it.<p>But that is where good parts end.<p>From the POV of real world boots-on-theground software challenges and developers it is a poorly designed, overengineered and overrated piece of complexity.<p>Complexity disconnected from reality of software engineering as a tool to serve business needs.<p>I can explain why this happens but I don’t want to get downvotes. People hate hearing bitter truth:)

Very useful document, thanks Pierre!<p>Our company is still on 2.13 and probably will be for a long time. The reality is that we need rock-solid library support across all transitive dependencies, and mature battle-tested tooling.<p>I like that the Scala language continues to improve, but its appeal in real-world enterprise applications took a hammering due to the backwards-incompatible changes in Scala 3, shaky tooling and ecosystem issues.<p>Also the elephant in the room - the Scala Center and toxicity within the Scala community.<p>The Scala Center Executive Director is a political sciences graduate with no commercial Scala experience, who gave this expletive-laden sexualised rant at a Scala conference:<p><a href="https:&#x2F;&#x2F;x.com&#x2F;jdegoes&#x2F;status&#x2F;1633888998434193411?s=46&amp;t=V_LFasefQl-Q0BteAGBqDg" rel="nofollow">https:&#x2F;&#x2F;x.com&#x2F;jdegoes&#x2F;status&#x2F;1633888998434193411?s=46&amp;t=V_LF...</a><p>When this ugly performance was called out by a member of the Scala ecosystem, it was the guy that called it out that got brigaded and cancelled, while the executive director Darja Jovanovic was defended by the community, and remains in place.<p>And then there&#x27;s Scala Center Community Representative Zainab Ali, who led an orchestrated witch hunt against a contributor to the Scala ecosystem. She ended up in the UK High Court for her role in this, and admitted fault (defamation) and settled.<p><a href="https:&#x2F;&#x2F;pretty.direct&#x2F;statement" rel="nofollow">https:&#x2F;&#x2F;pretty.direct&#x2F;statement</a><p>Like the executive director, the community rep remains in place at Scala Center:<p><a href="https:&#x2F;&#x2F;www.scala-lang.org&#x2F;ambassadors&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.scala-lang.org&#x2F;ambassadors&#x2F;</a>