Hi r/scala, Kannupriya here, co-founder of LLM4S.

Happy to share that LLM4S Foundation is collaborating with VIPS Technical Campus, Delhi!

I'll be speaking at their E-Cell event this Friday (23 Oct) about our LLM4S journey, building GenAI tools for Scala/JVM, and helping students get involved in open source.

I'll also be judging their student startup pitching competition.

If you're around Delhi, would be great to meet fellow Scala developers!

📍 VIPS-TC, Delhi | 23 Oct, 10 AM

https://llm4s.org

Here is the docs for my Godot Scala native binding https://optical002.github.io/godot-scala-native

I have been building for some time with my Scala language and I've reached a state where I don't need to add anything for building my games and features are already sufficient. Already made a steam deployment for steam, for windows/mac/linux and it seems to work all good, haven't found problems so far.

I'm sharing this if anyone wants to build games with Scala.

Happy to release a first version of Scivolo, a Scala Interpreter written in Rust. Unfortunately nothing was working at Scala Days, so it comes a week later.

Right now it interprets ~1140 of ~1710 of dotty's tests/run programs and passes 99% of Scala Native's precompiled NIR tests.

Performance is fine:

$ cat HelloWorld.scala
object HelloWorld {
  def hello(): Int = {
    42
  }
}

@main
def main(): Unit = {
  println(s"Hello World ${HelloWorld.hello()}")
}

$ time ./target/release/scivolo HelloWorld.scala  
Hello World 42
0,01s user 0,02s system 34% cpu 0,095 total
$ time ./target/release/scivolo HelloWorld.scala
Hello World 42
0,01s user 0,00s system 91% cpu 0,011 total

It also has an experimental AOT-Compilation path using Cranelift:

$ time ./target/release/scivolo-aot HelloWorld.scala -o HelloWorld
1,20s user 0,16s system 163% cpu 0,828 total
$ time ./HelloWorld # Slower, because OSX checks new binaries 
Hello World 42
0,00s user 0,01s system 3% cpu 0,245 total
$ time ./HelloWorld
Hello World 42
0,00s user 0,00s system 74% cpu 0,010 total
$ ls -lsah ./HelloWorld
9120 -rwxr-xr-x  1 nos  staff   4,4M 20 Okt 19:48 ./HelloWorld

The interpreter is using the NIR-Format (Version 0.5.x) of Scala-Native, because it is JVM independent and has an established, small C-Runtime. The AOT-Compiler compiles the NIR-Format using Cranelift into native executables. It is also reusing Scala Native's Standard library and calling coursier for dependency downloading.

There are no OS-Threads yet (only some green threads), and also some advanced features do not work yet. I got only one Macro to run (Circe's Object-Codec derivation). Only small snippets are exercised. The GC is the same as Scala Native (Immix).

Performance wise, there are some neat tricks: The whole Standard-library is mmaped into Memory, already search optimized. So there is basically no initialization overhead.

Disclaimer: The code is mostly unreviewed AI port of the Scala sources. It strives to generate Byte-Exact NIR-Code like the existing Scala Native Compiler. Use it for amusement.

Why? It all started with a small AI dialogue about why I can't have have fast (deployment) scripts in a typesafe language. Now I have.

Hello all! Released etl4s 2.0 + new doc (no AI). Thank you for the discerning eyes and feedback over these months 🙇‍♂️

The lib is now effect polymorphic, and models nodes/pipelines are Free Arrows.

Would say it is pretty much "done" for its intended production use cases now (mainly to guide OLAP programmers in big shops to write their programs as values)

The internals have been completely rewritten, but the public API hasn't changed at all. (To be fair, the API was very simple).

Chiefly, there is better pipeline introspection now, and nodes automatically capture val names and fully qualified class names.

I did my first ever presentation to an audience after almost 30 years in tech and leadership roles. It was a very rewarding experience and I look forward to the next time. You can see the whole talk here:
https://www.youtube.com/watch?v=lC1XP5tG0WE

Hi! I’m just starting to learn Scala. I work as a data engineer, and I have a fair amount of freedom to implement whatever I choose. I’ve gathered that many of you have extensive experience—any advice for a newcomer like me?

I've been building a personal expense tracker by directing AI agents instead of writing the code myself.

Stack: Play + PostgreSQL on the backend and Scala.js on the frontend. Receipt OCR and bank statement extraction use AWS Textract/Bedrock.

Fair warning: the code is messy and my AI workflow is far from ideal. That's part of why it's public.

Curious how others are using AI agents on Scala codebases, and where it works or falls apart for you.

Repo: https://github.com/AlexITC/expense-tracker

Write-up: https://alexitc.com/blog/2026-10-16-opensourcing-my-expense-tracker/

Hi everyone!

I'm preparing for a Scala 3 programming test for a T-Bank internship program, expected on November 8. I'm new to Scala, but I already have some experience with Python.

I'm currently learning Scala 3 basics, including variables, loops, functions, collections, "map", "filter", and simple algorithms. My goal is to become comfortable enough with Scala to solve beginner-level coding problems independently.

I'd also like to use AI tools like ChatGPT effectively as a learning assistant, rather than relying on them to write solutions for me.

I'd appreciate your advice on a few questions:

1. What should I focus on first? Which Scala 3 topics are essential for a beginner preparing for a coding test?

2. How should I practice? Are there any good resources, websites, or LeetCode problems suitable for someone new to Scala?

3. How can I use AI effectively? For example, should I ask it to explain concepts using Python comparisons, generate exercises, review my code, or simulate a technical interview?

4. What mistakes should I avoid? Is it better to focus on understanding Scala syntax and collections first, or start solving algorithmic problems right away?

5. What would your study plan look like for the next three weeks? I want to make consistent progress without trying to learn everything at once.

If you have experience preparing for Scala interviews or using AI to learn a new programming language, I'd love to hear what worked for you.

Thanks in advance!

Hi everyone!

I'm currently preparing for a Scala 3 programming test for a T-Bank (Tinkoff) internship in November.

I'm a beginner in Scala, but I already have some experience with Python and basic programming concepts.

I'm looking for:

- Previous interview experiences from T-Bank Scala internship candidates

- Examples of coding tasks and technical questions

- Information about the topics covered in the programming test

- Any public repositories, GitHub collections, or community resources with practice problems

If you've applied for a Scala internship at T-Bank or know where I can find relevant materials, I'd really appreciate your help!

Thanks in advance!

I am considering learning Scala due to its very advanced functional programming features and the large Java ecosystem it can use. I have many years of programming experience in various languages. Scala has some FP style constructs that will challenge me a lot, but that would be part of the fun. In case it matters, I write my programs by hand.

The question I want to ask is, how many and if any at all new green field projects have been started with Scala 3 during the last 1-2 years. I.e. does Scala remain a popular and widely adopted language or it is more in decline?

Thanks a lot in advance

EDIT: Thank you so much for all the helpful replies and the objective assessment.

Hello everybody, I'd like to let you know about a recent experiment/POC I've been working on recently:

Safe Scala is a recent experimental feature. In short, it is a subset of Scala which doesn't allow for any sideffects. Any sideeffecting tools, especially Java standard library are just not aceesible -- a program using those won't compile. Thus the only way to peform side effects is via explicitly passed in Capabilities. That may sound like a pure academic excercise.

But there is a project called Dapr which is aiming to abstract cloud applications from the hassle of I/O (queues, sync messaging, distributed locks, state, durable workflows, etc.). Thus allowing apps to focus on business logic and use dapr as a framework (running out of the app process). What if we could represent these capabilities of Dapr as Scala Capabilities?

That's exactly what dapr4s does. It uses Dapr's Java SDK behing the scenes but exposes a pure Capability-style Scala facade. It is still just an experimental project, nothing ready for production (at least just yet). But it's a POC -- a proof that Safe Scala can be practical to build (maybe even line of business boring) cloud apps.

Here's the link to the project:

https://github.com/sideeffffect/dapr4s

Repository with examples and a slides with more info:

• https://github.com/sideeffffect/dapr4s-examples
• https://github.com/sideeffffect/dapr4s-examples/blob/master/SLIDES.md

I hope you'll find this project inspiring and would be happy to discuss details at Scala Days 2026 in Berlin.

(Disclosure: the project has been developed with the help of LLMs.)

🚀 Introducing Scala Packages: https://pkg.scalanews.net

A fast, modern search for Scala libraries:

🔍 Every Scala library on Maven Central: JVM, Scala.js, Scala Native, and sbt & Mill plugins 🆕 New projects and new releases on the home page, plus an Atom feed 🧩 Free JSON API, no key needed 🤖 MCP server, so AI assistants can search packages and fetch install snippets: claude mcp add --transport http scalapkg https://pkg.scalanews.net/mcp

It complements Scala News (https://www.scalanews.net): the newsletter for what the community is writing, and Scala Packages for what it's releasing.

Hi all, we at Deezer work a lot with Scala and today I published a blog post about some fun things we've done with it.

TLDR; the search at Deezer was clogging up our cache systems. We significantly improved the situation by changing the serialization format of the cached payloads, and rolling out a tailor-made, space-efficient and blazing fast data structure inspired by Hash Array Mapped Tries.

If you're still on Scala 2 and were worried that it might stop being maintained, worry not! Of course, if you need help migrating to Scala 3 we are even more happy to help.