okay folks, new module out of the oven 🍞
kyo-ui 🧩
write a UI once, run it on the client or the server:
▸ Swap the runner: the same UI mounts in the browser on Scala.js, streams from a server over SSE, or renders to static HTML for SSR and tests.
▸ Reactivity without the machinery: a Signal is a plain value you pass wherever the API takes one, with no wrapper type, binding operator, or hooks.
▸ Type-safe down to the markup: containers accept only valid children, attributes are enums instead of strings, and setters exist only where they apply.
▸ Surgical updates: no virtual DOM and no re-rendering, only the nodes a changed signal touches get patched.
JVM, JS, and Native. Of course 😎
After over a decade without writing a new DB library, I finally had the time to iterate on a new approach 😅
Quill has long lasted as the richest DB library in Scala, but it's time for some innovation! 🙌 kyo-sql is in the oven and packed with goodies:
✅ DSL mirrors SQL syntax, not collection algebra
✅ Records properly encode relational algebra: no nested tuple nightmare anymore 🥹
✅ Raw sql fragments that compose with other typed APIs
✅ Single compilation pipeline, three execution modes: run/runStatic/runDynamic. Full control with peak performance 📈
✅ No complex macros or transformations of queries. A simple, reliable and predictable compilation process
✅ Native async PG + MySQL drivers in pure Scala, first-class typed cancellation, no JDBC
✅ And yes! support for JVM, JS, and Native 😱
This is so much fun!!! 🚀🚀🚀
(don't miss the preview 👇🏼)
Scala has long been a magnet for innovation and, although that's actually desirable, the consequent fragmentation of the ecosystem is a major issue for library authors. And yes, Kyo worsens it.
It's time for a proper solution! Forget F[_], meet kyo-compat: write your library once, support ZIO, Cats Effect, Future, Ox, Twitter Future, and Kyo 🪄
✅ Zero overhead: every method is inline and lowers to the backend's own primitive. No typeclass dispatch
✅ No degraded features: capabilities like tracing work as if using the underlying libraries directly
✅ Fully isolated: each artifact depends only on its target library. No Kyo runtime, zero dependencies
✅ SBT plugin: cross-publishes every backend from one source tree
One source. Every stack.
Zero-cost, type-safe Spark data pipelines! 🚀 No, I'm not talking about Frameless, but Wick: an internal tool from @NetflixEng which has been open-sourced! Huge credit guys for sharing this with the community! ❤️
Go check out ZIO Blocks! It's a collection of independent libraries with zero or minimal dependencies. Despite the name, ZIO is not needed to use them. ☝️ https://t.co/6y05fL4m6c
https://t.co/KJTluH1vwO
Scala Roadmap for learning is now officially published. It contains over 150 nodes with descriptions and links to learning materials. It's aimed at beginners but I'm sure many advanced developers can find there something for them as well.
Please share😊
🚀 The Scala bytecode optimizer just got ported to Scala 3!
Write nice high-level code and let the optimizer make it faster.
Try it out today in Scala 3.8.3-RC3!
https://t.co/kZRv6LCJXp
If you're using macOS and Homebrew, we have some great news for you! Thanks to the great work by Piotr Chabelski, installing Scala via Homebrew now includes native-image binaries.
This means the CLI starts faster and doesn’t require Java to be installed on your machine.
I wrote my first blog post ever
476 words. 2 min read.
It's about the simplest trick I keep repeating to fellow developers — and it works every time
https://t.co/FWv8Al6N9Q
We love to complain about the Scala 2 -> 3 migration.
But let's be real: an older compiler (2.13) natively consuming libraries from a newer one (3.x) for 5 years is pure engineering witchcraft. 🪄
What other language ecosystem even attempts a migration strategy this ambitious?
🚨 With Scala 3.8, this forward compatibility is officially ending. Don't panic, though.
✅ Backward compatibility remains rock solid - Scala 3 still happily consumes your existing 2.13 jars.
@matej_cerny I’m not using it to generate a blog at this time but I do use it to generate internal documentation from code comments. Super handy.
I also use SwaggerDocs on http routes via the OpenApiGen in zio-http
ScalaDoc static site:
https://t.co/0tzjYOnOJ6
Shoutout to @jdegoes and @aplokhotnyuk for the solid fundamentals + killer performance work that got us here.
Recently, John and I went wild with fresh features + micro-libs 🔥
The goal: blazing high performance + excellent DX + plain Scala.
Zero ZIO deps. Zero anything else.
https://t.co/iOQCoBFIjq
The Sovereign Tech Fund Invests in Scala:
🔐 security audits
🔧 sbt 2.0
📚 core library maintenance
💪 and long-term resilience for critical digital infrastructure
Check out the announcement: https://t.co/MJLE9BfzZI
🙏 Huge thanks to Sovereign Tech Agency
New Metals 1.6.5 is out!
- Completions for implicit classes
- Auto-imports for Java
- Streamable HTTP standard for MCP
- Type hierarchy support
Check out more at https://t.co/thxuTNYto8
If you're using Scala 3 and want to stay updated with the latest versions, we have two key reminders for you! First, the upcoming Scala 3.8.0 will be released using JDK 17. You can find more details in last year's Scala blog at https://t.co/gQ4hSfZOnk.