Hi, I'm happy to announce that I'm here to help your Scala team and Scala-based products succeed. I will be available for any questions, suggestions and complaints during my open hours that should start this week (TBA soon). PMs are open. I'm also available on Scala, Typelevel and ZIO discords.
We're scaling up our commitment to #Scala3 by introducing new roles that will drive innovation and community engagement.

Feb 5, 2024 · 1:36 PM UTC

1
20
87
Replying to @lukasz_bialy
Hey, this is great to hear! Let's start with the hardest question. It would be good to hear about the long-term commitment to Scala 2. A lot has been said about Scala 3, but a huge number of companies are still on Scala 2 with no plans for migration for various reasons.
Shooting the big guns first, huh? Ok, let's discuss this. Current situation is that 2.x branch is not actively developed anymore and receives some backports from 3.x, migration-oriented utilities, security patches and bugfixes. This is even more limited for 2.12 which gets security patches and minor bugfixes only. Lightbend's Scala team is responsible for 2.x branch and as far as my knowledge goes there aren't any plans to drop this support in the immediate future. Now what is more pressing for us here at VirtusLab is to understand what the blockers for the migration process are and to support companies in the move to Scala 3.3 which is the current Long Term Support release. We've been quite busy doing this via both open source contributions that helped libraries to migrate to Scala 3 but also by our offer of free-of-charge consulting by migration specialized engineers. We are aware there are several reasons why folks are apprehensive of the move and we want to help however we can. I'm also paid to mention that we're providing commercial compiler support services 😉
1
4