Pierre Ricadat

Do you like Caliban? Or maybe Shardcake? Enjoyed OSS contributions I’ve done over the years? Have I helped you on Discord? I’ve just setup a GitHub Sponsor page so if you’d like to give a little back or encourage future contributions, head up to github.com/sponsors/ghost… 🙏

Migrated some heavy ZValidation logic to the PureLogic Writer capability today. Deleted 1,300 LoC (15% of the file) with a 20% speed gain and -63% allocations.

@novalevys if you share a scastie i can take a look

@ghostdogpr sbt compile doesn't work

Introducing PureLogic: a direct-style, pure domain logic library for Scala! I embraced Scala 3 capabilities to build a direct-style alternative to ZPure/RWST/MTL for writing pure domain logic with no syntax overhead, insane perf and good stack traces. blog.pierre-ricadat.com/introducing-pu…

@NicolasRinaudo @riccardo_cardin 3.8 basically :D

@ghostdogpr @riccardo_cardin I dont know what scala next is!

The first version of the article on Effect Systems in #Scala had some criticism and comments. We learned from them and tried to review the content to express better the differences among functional and imperative programming, direct-style, and a future-like approach. Here is the new version: rockthejvm.com/articles/the-e… As usual, thanks to @rockthejvm for the opportunity 🙏

@NicolasRinaudo @riccardo_cardin Oh I see, `-language:experimental.captureChecking` is not related to `-experimental` (which is transitive). Then I guess the only constraint for the library is to depend on Scala Next rather than the LTS (but the new LTS is coming soon anyway).

@ghostdogpr @riccardo_cardin Ah i see. No, they don’t. For example: in 3.8, the entire stdlib uses capture checking, yet you, as a code author, still need to explicitly turn it on in your own code. It’s not a transitive flag.

@NicolasRinaudo @riccardo_cardin If the library uses capture checking, anyone that depends on it requires the -experimental flag at this point. But that would be nice to not force users into it and let them use the library with capabilities but without capture checking if they wish to. Does that make sense?

@ghostdogpr @riccardo_cardin What would be the point?

@riccardo_cardin @NicolasRinaudo One thing I wonder as a library author is whether there is a way to cross compile with/without capture checking or if you have to make the library require the experimental flag.

@ghostdogpr It's in the planning: github.com/rcardin/yaes/i…. However, I haven't tried it yet since @NicolasRinaudo promised to give me help during Scalar 2026 😝 BTW, if you want to join the party, you can always open a PR 🙏

@novalevys AI definitely helps but I understand/trust all the code I ship =)

@ghostdogpr are you converted vibe coder?)

I haven’t even publicly announced my 3rd library yet and I’m already working on the 4th 😅

@NicolasRinaudo @riccardo_cardin I see, thanks! Looking forward to seeing your talk at Scalar!

@ghostdogpr @riccardo_cardin Definitely useful. Handlers are not generally pure, most of the useful ones will carry mutable state. This could be a resource - a file, say, for a “Printer” capability. Without CC, some computations might close over the handler and expose it after the resource is closed. 💣

@guizmaii One’s about Protobuf/gRPC, the new idea is related to pure domain logic.

@ghostdogpr What are they about?

@adamhearn Is it using sbt —client ir spawning a new one?

Nothing makes my macbook hotter than the Scala 3 compiler. Parallel agents need their own EC2 instances...or maybe I should just stick to Typescript and Effect

@adamhearn I think the announcement from Flavio that he was stepping away a few months back made it seem like it was abandoned and that 1.0 wouldn't happen (also no new release since then comforts that sentiment). Glad to see there's some activity recently!

It's unsurprising, yet still disappointing to see Kyo excluded from the State of Scala survey. Plenty of smaller libraries (Ciris, Scribe, Magnum, etc) are included, but I don't think this is about size. Why does Ox make the cut but Kyo does not?

"The actual path to seniority isn’t learning more tools and patterns, but learning when not to use them. Anyone can add complexity. It takes experience and confidence to leave it out." An éloge of simplicity that resonated deeply.

@wnwbbprv4p @fbrasisil With sbt —client it’s quite fast

@fbrasisil Still horridly slow.. every sbt command slows everything down And let’s be honest the models just aren’t nearly as good with it vs other languages

A nice plot twist: Scala's bad DevEx is greatly mitigated by AI agents. I don't bother with broken IDE refactoring, don't need to fight sbt anymore, don't need to debug stuff because of bad docs, can easily pinpoint compiler bugs and find workarounds, etc. Just ship 🚀🚀🚀

@Krever01 @guizmaii @scala_lang Coming soon scalar-conf.com/talk/protobuf-… 😄

@ghostdogpr @guizmaii @scala_lang What's the lib? 😅 But yes, I strongly agree, all my libs are Scala3-only.

That's it I dropped the support for @scala_lang 2 from all my little Scala libs (that probably no one uses except me anyway) It's time 2026 is the time to drop Scala2 and JDK11 support It'll help people stuck with Scala 2 to have good arguments to justify migrating to Scala 3

We're running the 2026 #Scala Survey! Let us know how you are using Scala, #AI with Scala, and give hints to the Scala teams (both at @VirtusLab and @EPFL) on where the focus in driving Scala forward could be. Thank you - your answers count :) virtuslab.typeform.com/ScalaSurvey2026

@Krever01 I replaced some Mirror-based inline validation with a macro which allowed better error messages, reduced bytecode and faster compilation. Felt great!

@ghostdogpr Same! Although I still try not to do it if I can 😅

Coding agents gifted me the power of writing Scala macros, I feel unstoppable.