←back to thread

Scala 3 slowed us down?

(kmaliszewski9.github.io)
261 points kmaliszewski | 4 comments | 07 Dec 25 15:08 UTC | HN request time: 0.2s | source
Show context
game_the0ry ◴[07 Dec 25 16:38 UTC] No.46182978[source]▶
I am not a scala fan and do not care for it, but I upvote for the thorough thought process, breakdown, and debugging of the problem. This is how technical blogs should be written. AI aint got shit on this.
replies(1): >>46185196 #
1. sema4hacker ◴[07 Dec 25 21:12 UTC] No.46185196[source]▶
> I was refreshing one of our services. Part of this process was to migrate codebase from Scala 2.13 to Scala 3.

My first question was: why?

replies(3): >>46186172 #>>46188205 #>>46188548 #
2. pxc ◴[07 Dec 25 22:54 UTC] No.46186172[source]▶
Scala 3 is sorta a new language, bringing a lot of improvements to the type system: https://docs.scala-lang.org/scala3/new-in-scala3.html

It also looks like it has some improvements for dealing with `null` from Java code. (When I last used it I rarely had to deal with null (mostly dealt with Nil, None, Nothing, and Unit) but I guess NPEs are still possible and the new system can help catch them.)

3. dionian ◴[08 Dec 25 04:11 UTC] No.46188205[source]▶
Why not though the upgrade process from 2.13 to 3 is pretty smooth. And you get all the new language features. I can think of a few that I actually like. I’ll just mention enums because it’s a good example.
4. lmm ◴[08 Dec 25 05:00 UTC] No.46188548[source]▶
If you're going to "refresh" a codebase you probably want it to be on the current version of things. Old dependencies rot, like it or not. I don't think there's any timeframe for Scala 2 EOL yet, but new development is happening in 3.