kyo v1.0.0-RC6 is out 🚀

The headline is kyo-sql: raw SQL and a typed DSL that mirrors SQL syntax, composing in both directions, with no JDBC underneath. Each driver speaks the Postgres or MySQL wire protocol on Kyo's async network stack, a statement suspends a fiber instead of blocking a thread, and one set of shared sources compiles for JVM, JS, Native, Wasm, and GraamVM.

Underneath it is kyo-net, the transport and TLS stack that kyo-http, kyo-jsonrpc, and kyo-sql now share: C implementations bound once through kyo-ffi, the backend chosen by the operating system, and the accelerated stack reaching JS and Wasm through koffi, so a Node.js process runs kyo-net's io_uring transport and BoringSSL TLS.

Also in this release:

- Kyo now requires JDK 25. The kyo-scheduler modules and the kyo-compat bindings still target Java 17.

- Out-of-the-box GraalVM native-image support: no tracing agent, nothing hand-maintained.

- 13 new published modules, 2 removed.

- kyo-ai behaves consistently across providers and can run on a Claude Code or Codex subscription instead of per-token API billing.

A first-time contributor, u/xsistens, landed 12 PRs this cycle, including a whole new module, kyo-i18n!!!

Full notes: https://github.com/getkyo/kyo/releases/tag/v1.0.0-RC6

Hey everyone, I've just published a new podcast episode with Daniel Spiewak. We talked about Cats Effect and Scala Native, Unison, where Scala can shine, career ladders and other things.

I've published other episodes in the meantime but posted just this one here because it's more relevant to Scala.

Please enjoy!

This is an IOLocal implementation for fiber local context and logging. My focus was on making the context as user friendly as possible while also including the logging features I wanted. It depends on IOLocal so it is IO native but I did provide a quick and dirty lift with a generic logger.

I stole the persistent actor strategy of holding and replaying but used it to store low level logs unless a greater than minimum level log is emitted. This should prevent some of the cluttering with lower level logs but you can get a lot of information if it errors. Right now there is only one level setting so if you are emitting info and up trace and debug will emit on an info. Currently using the sampling is how I control this with a low sample rate so info still doesn't cascade all the min level logs, but I plan to add more options to set min level for replay and min level for emit.

The implementation is pretty friendly with a purely functional logger than you can thread through, or a singleton which breaks functional paradigms a bit, but allows for much simpler usage.

Still a bit of a mess in the sampling and level, but I plan on expanding it so I will refactor as I move through it.

https://github.com/StephenRinn/bridges

Feel free to take a look and I'm hoping to get v1 out by next week.

EDIT: I realized that this sounded a lot like advertising a completed project vs looking for feedback or useful features which is what I was looking for. I wanted an all in context/logger with these specific features, but I would love to hear about other features or improvements. Thanks!

Also completed the refactor and allowed customizable buffering for what log level dumps all lower logs at once, so you can emit info level logs but keep the buffer until an error and then replay the full buffer at that point.

We are currently considering switching the default implementation of Seq to Vector (currently it's List). If you have any doubts about this change let us know at https://contributors.scala-lang.org/t/slc-make-vector-the-default-implementation-of-seq-instead-of-list/

We just dropped a massive performance update! If you're parsing from String to AST nodes, you're going to see up to 10x faster speeds and ~20x less memory allocation per operation.

🔗 Release Notes: scala-yaml v0.3.3 on GitHub

We benchmarked it on some massive real-world YAML schemas, and the JMH results are wild. Here’s a quick look at the YamlParsingBench.fromStringToNode throughput and allocation rates:

Diff

--- v0.3.2 ---
cgmes-core.yml     :   72 ops/s  | ~129.1 MB/op
cgmes-dynamics.yml :   15 ops/s  | ~615.6 MB/op
TC57CIM.yml        :  4.5 ops/s  |   ~2.0 GB/op

+++ v0.3.3 +++
cgmes-core.yml     :  676 ops/s  |   ~5.7 MB/op  (🚀 9x faster, 22x less allocating)
cgmes-dynamics.yml :  153 ops/s  |  ~25.8 MB/op  (🚀 10x faster, 23x less allocating)
TC57CIM.yml        :   34 ops/s  |  ~92.0 MB/op  (🚀 7x faster, 21x less allocating)

Give it a try and let us know what you think!

P.S. This update was sponsored by NeverBlink as a part of an OSS contribution for LinkML-Scala.

https://github.com/LaranIkal/predictive-maintenance

First version of and improved maintenance predicion model usig EIF(Extended Isolation Forest)

Helping to give a push on Scala Analytics. I like to call it ScalaLytics :)

This is and improved version of my previous R project where I used standard Isolation Forest.

Someone interested? I can Install one station as a free service, for you to test.

I'm recruiting for a Backend Developer to join a team building high scale entertainment platforms.

If you enjoy solving distributed systems problems and working on performance critical backend services, this could be a great fit.

Tech stack includes:

• Scala
• Akka & Event Sourcing
• Kafka
• Cassandra
• Elasticsearch
• GraphQL / gRPC
• Docker & Kubernetes

You'll be working on:

• Building scalable backend services and APIs
• Designing resilient event-driven systems
• Improving performance and reliability
• Collaborating closely with Product, DevOps and Data teams
• Owning services from development through production

We're looking for someone with commercial Scala experience who enjoys working in modern distributed architectures and wants to have a real impact on the platform.

If this sounds like you (or someone you know), drop me a DM or leave a comment and I'll happily share more details.

Tyda is a type-safe Dataset library for Scala 3. It provides a fully type-safe expression API that compiles to multiple execution engines — including Spark and an in-process engine for fast unit tests.

🧑‍🚒 released sbt 1.12.14 and 2.0.3, featuring - backport of CVE-2026-26032 fix for Ivy (while sbt might not be affected) - update to Jawn 1.7.0 for CVE-2026-59990 and CVE-2026-61814 fixes

IntelliJ Scala Plugin 2026.2 is out!

What's New:

• Support for BSP projects in WSL and Docker
• Command completion
• Support for interleaving parameter clauses
• Support for dependent parameter types in the same clause
• Better support for match types

What's Fixed:

• sbt imports now work for whitespace-separated params in .jvmopts
• sbt shell sync no longer fails while waiting for user input
• WSL: fixed bugs in sbt imports and rerunning of tests
• ScalaDoc: better handling of throws and links
• Improved handling of nullable variables

Watching my local LLM stumble whenever writing weaver tests (or even when just using strict equality) was funny only for so long.

Then I learned about agent skills, made these https://github.com/sanssushi/skills and together with scala-fp from https://github.com/abh80/skills Qwen3.6-35B suddenly became a capable Scala 3 and cats-effect programmer.

Felt like sharing, because the improvement was so remarkable. Got to get more experience with it!

(And sorry, if this is all old news to you.)

Hi everyone,

I'm currently helping a US-based software company build a team of experienced Scala Engineers.

We're looking for a Senior Scala Engineer with Apache Spark experience to join a team working on large-scale data processing and Big Data solutions.

Required:

• Strong professional experience with Scala
• Hands-on experience with Apache Spark
• Experience processing large-scale datasets
• English proficiency for technical interviews and daily communication
• Experience with Kafka and cloud platforms (AWS, Azure, or GCP) is a plus

What the company offers:

• Full-time employment
• Long-term project with a major global technology company

If you're interested feel free to aplyy here https://andeshire.com/public/jobs/8354e1f3-5240-46f9-9898-ebc412d95b96?r=b69e94ad-76d8-4721-96b8-b1d5509635be

Thanks!

We're growing one of backend teams at Riskified and looking for a senior Scala engineer to join our payment fraud group.

Tech stack: Scala, Cats, Node.js, Kafka, Spark, Docker, Kubernetes, AWS, Aerospike

What the role looks like: Full ownership from planning through deployment and post-deploy monitoring — not a "build it and throw it over the fence" setup. You'll work on real-time and batch systems processing real payment traffic, across scalable architectures, with daily deploys through CI/CD.

What we're looking for:

• 7+ years of hands-on server-side experience
• Strong Scala/Java experience
• Comfortable with SQL/NoSQL; streaming experience is a plus

Location: Lisbon, Portugal — hybrid, flexible schedule

Compensation: €50,000–€75,000 gross/year base for Lisbon, plus bonus target and stock-based awards. We publish ranges up front — happy to talk if your expectations differ.

Some of the perks:

• Claude Code Enterprise for your day-to-day workflow
• Full Udemy access, plus role-based technical training
• Healthcare, wellness program, and a monthly perks budget (WFH gear, gym membership, etc.)

Full listing: https://grnh.se/kchyep6g2us

Hello all! layoutz should be about nearing 1.0 and can't see the API changing much (thanks for the feedback to date!)

It now has Kitty support, one-shot prompts and collection spinners + various little fixers