Zero-allocation, type-safe state management is possible on the JVM with Scala 3. Kyo leverages this in `Safepoint`, an internal mechanism for stack safety, thread isolation, and debugging. Thread depth, interceptor presence, and ThreadId are all tracked in a single `Long` via

Besides that confusing article, it looks like GraalVM CE and NI are on their way.

GraalVM Native Image is being discontinued for Java SE Product customers. The JDK 24 was the last. Option: transition to JIT alternatives.

Soundness is still pretty unknown, yet an underrated ecosystem of libraries. Great to see it getting more exposure so more developers can discover it.

Hey @softwaremill and @adamwarski 👋 How do you rate this DeepWiki answer quality https://t.co/N4qWkJNza9 BTW - have you considered adding the Ask DeepWiki badge to tapir, sttp, quicklens, etc? Could be interesting to let users talk to your docs!

Hey Scala folks! 👋 The avro4s needs help with a publishing blocker 🛠️ Probably a quick fix for someone with experience - release with Scala 3.3.6 is waiting! Anyone willing to help? https://t.co/eTegM0R13J

Released Version 1.0.0-RC3 of the Mill build tool for #Java and #Scala. Last release candidate before 1.0.0 final which is due next week 10th July, so please try it out! https://t.co/wi9KfzvM6P

Also, even though these days people like to joke about Uncle Bob, what I’ve done here feels like a decent example of the Open-Closed Principle from SOLID. I just add another given and everything keeps working. If I miss something, the compiler lets me know right away.

Worth adding, that was a sketch code. I can further generalise some, e.g. for numerics and iterables, so that I don't have to implement explicitly an action for each one: Double, Int, BigDecimal, etc., and similarly List, Set, Seq, etc. Useful little implementation. Why I need

I wanted to implement type-checked paths—something like what I’ve seen in `.ignoreAt` from the Diffx library, or in QuickLens. Should I use a compiler macro? Magnolia? Or maybe there’s a way to use QuickLens in a more abstract way. Of course! And I didn’t have to write any macros

Fresh from a Sunday walk, I decided to tackle my second Scala 3 macro ever! 😀 My goal: automatic `difflicious.Differ` derivation for opaque types, making using Difflicious seamless. This bridges a gap in Magnolia's current support. Until this Magnolia issue

Took my first steps with Scala 3 macros to solve a real problem: Magnolia's lack of support for automatic `AnyVal` derivation. Wrote a simple macro to handle it. It felt surprisingly straightforward! 🔹Am I missing any obvious pitfalls? 🔹Is this approach too naive? 🔹Also,

This is awesome! With Chimp library and #Scala-CLI stack creating an MCP server is so straightforward! https://t.co/583pzBHgyE

Last week, I attended the #AWS Summit Hamburg, a truly massive and well-organised event! Beyond the inspiring presentations, I visited the Ask An Architect booth. We discussed some limitations and explored what we needed to unlock new possibilities. And today I just received an

Scala 2→3 migration going smooth! 🚀 Dozens of microservices, e.g. 37kloc pure Scala (286kloc total) with mostly business logic, or in-house libs e.g. 28kloc (60kloc total) with a bit more advanced code. It's maritime logistics industry. Step 1: -Xsource:3 for migration warnings

QSpace Pro at first seemed too Finder-like (which I really don’t rate), but it’s just the look—functionally, it’s next level. Only wish: could hide Finder dock icon.

Spent some time today checking out Total Commander alternatives for Mac. ForkLift I knew, Commander One is cool, but QSpace Pro wins for me. It's super flexible. Anyone else tried it or found something even better?

I just completed a very smooth migration from Diffx to Difflicious. I have several add-ons that I'll likely propose as new features in the form of MRs. #scala #testing

TIL: In Scala `trait` can extend `class`. https://t.co/8FIzkr07Ga and further in this thread another use-case

I just realized I didn't mention the most important thing about @bishabosha talk - it's also about the DX and ergonomics offered by these solutions. It's not just about convenience for library authors. It also focused on highly ergonomic solutions for users of these libraries.