[Talk::Overflow #20] Scala Days 2025 Tech Talks

Welcome to the 20th edition of Talk::Overflow!!

Scala Days 2025 in Lausanne reads like an ecosystem taking developer experience seriously—without giving up the things that make Scala powerful. Across keynotes and tracks, the repeated theme is making advanced ideas feel usable: capability-based safety, direct-style programming, faster builds, and tooling that reduces the gap between ‘it compiles’ and ‘it ships reliably’. If you’re building JVM services, libraries, or developer tooling in Scala, this year’s program is a snapshot of where the language and community are investing next.

The object capability model has been established since the 1960s. It then goes deeper on the mechanics: It is probably the most obvious and clean way to protect trusted from untrusted components in a complex system. The key topics called out are type system, capabilities. What’s useful here is that the scope stays concrete: you can map the idea to code structure, APIs, and the failure modes you actually debug.

How many companies miss out on functional languages because they do not know how to find functional programmers? It then goes deeper on the mechanics: After interviewing engineering leadership at four companies that have used Elm successfully, I found that they all independently chose to hire people without Elm experience and all got them fully onboarded in about four weeks. (That is competitive with the time it takes to onboard into a JavaScript/TypeScript project with particular in-house conventions and library combinations.) That means they get all the benefits of functional programming while still drawing from the largest possible talent pool. The key topics called out are the core ideas. What’s useful here is that the scope stays concrete: you can map the idea to code structure, APIs, and the failure modes you actually debug.

Rust is primarily known for its ownership-based type system that enables a low-level programming paradigm in a type-safe language. It then goes deeper on the mechanics: However, another key pillar of Rust is its treatment of unsafe code : while most languages tend to shun unsafe operations, often leaving them poorly specified, Rust gives unsafe operations a lot of attention, from a dedicated syntax to documentation and community norms. The key topics called out are type system. What’s useful here is that the scope stays concrete: you can map the idea to code structure, APIs, and the failure modes you actually debug.

The Scala 3 type system is powerful, but to use it effectively, you need to understand it. It then goes deeper on the mechanics: This talk offers a guided tour of its major features, covering types, bounds, kinds, variance, type lambdas, type and kind lattices, polymorphic functions, abstract types, and wildcard type arguments. The key topics called out are Scala 3, type system. What’s useful here is that the scope stays concrete: you can map the idea to code structure, APIs, and the failure modes you actually debug.

What do functional programming and Johann Sebastian Bach’s music have in common? It then goes deeper on the mechanics: More than you’d think. The key topics called out are the core ideas. What’s useful here is that the scope stays concrete: you can map the idea to code structure, APIs, and the failure modes you actually debug.

You’re reading [Talk::Overflow #20] Scala Days 2025 Tech Talks — the weekly digest for developers who want to stay sharp and skip the noise.
→ Browse past issues
→ Suggest a talk
→ Share it with the friends

Stay curious. Stay kind.

— Talk::Overflow