We are aware that this survey isn’t perfect; it has blind spots - but it is better to reason based on some results rather than base your judgments just on one’s feelings and experience -  no matter how vast it is. We would love to capture 10x more responses, so if you miss the survey, please reach out - we are open to hearing any voice.
See the full report now: https://lp.virtuslab.com/landings/scala-projects-maintenance-survey-report/

#VirtusLab #ScalaDevelopment #ScalaCommunity #Scala3 #ScalaSurvey

Scala Projects Maintenance Survey Report - VirtusLab.com

Scala Projects Maintenance Survey Report

VirtusLab.com
The average Scala project has been around for 7 years, with the median being 6 years.
This highlights Scala’s staying power in long-lived systems, but it also means fewer new projects are starting with Scala.
It’s clear we need to do more to make Scala appealing for new beginnings. What can we build together to change that?
#ScalaSurvey
Contrary to the complaints you might hear, the Scala community is largely satisfied:
49% of developers are happy, and 44% are rather happy with Scala.
And when it comes to future projects, over 88% would consider using Scala again ❤️. #ScalaSurvey
How do Scala projects handle libraries?
53% mix multiple ecosystems (e.g., Akka + Cats), while 36% stick to a single ecosystem (e.g., only ZIO). Interestingly, 11% avoid ecosystems entirely, relying on the stdlib or proprietary frameworks. Interop between libraries seems as relevant as ever. #ScalaSurvey
Monorepos or separate repos? The Scala community leans toward separate VCS repositories - 65.5% prefer this approach, while 34.5% stick to monorepos.
Interesting how sbt dominates even considering the amount of monorepos 🤔 With sbt soon supporting Bazel's caching protocol, things are going to get even more interesting!
#ScalaSurvey

When it comes to IDEs, Scala developers have a favorite:

IntelliJ IDEA remains the top choice, with 61% of projects using it exclusively and 83% projects having it as a popular developer choice. Metals are popular in 25% of projects but only 8% of projects use them exclusively.
IntelliJ keeps holding strong.
#ScalaSurvey

The Scala build tool landscape in 2024: sbt remains the cornerstone for Scala projects, powering 87% of them. scala-cli, however, is gaining traction, now adopted by 11%. Curiously, almost 8% of projects use Bazel now!

With sbt as the heavyweight and scala-cli rising fast, there's room for both versatility and simplicity in the ecosystem.
#ScalaSurvey

Who’s working on Scala projects? Experienced devs dominate the field: Scala teams tend to be senior-heavy - over 54% have mostly senior developers.

This highlights a challenge: we need to make Scala easier to learn and more accessible. We’re working on it!

#ScalaSurvey

We’ve noticed a sentiment that Scala’s complexity might hold teams back. So, we asked if you feel that way, and the answer is clear: 80% of Scala devs say their project’s use of Scala doesn’t hinder productivity.
However, there’s more to the story—stay tuned. #ScalaSurvey
How do teams approach Scala in practice?
- Purely functional Scala leads with 38% of projects.
- Regular stdlib + utils Scala follows closely at 35%.
- Generic-heavy, type-level Scala accounts for 20%.
- Pythonish/Java-like Scala rounds it out at 7%.
#ScalaSurvey