Pierre Ricadat

1.7K posts

Pierre Ricadat banner
Pierre Ricadat

Pierre Ricadat

@ghostdogpr

Software Architect | Scala Lover | Creator of Caliban and Shardcake

Seoul, Republic of Korea Katılım Haziran 2007
98 Takip Edilen1.5K Takipçiler
Sabitlenmiş Tweet
Pierre Ricadat
Pierre Ricadat@ghostdogpr·
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… 🙏
English
2
19
54
7.4K
Pierre Ricadat
Pierre Ricadat@ghostdogpr·
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…
English
3
23
89
5.5K
Riccardo Cardin
Riccardo Cardin@riccardo_cardin·
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 🙏
English
1
8
56
3.7K
Pierre Ricadat
Pierre Ricadat@ghostdogpr·
@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).
English
1
0
0
39
Nicolas Rinaudo
Nicolas Rinaudo@NicolasRinaudo·
@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.
English
1
0
0
38
Pierre Ricadat
Pierre Ricadat@ghostdogpr·
@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?
English
1
0
0
33
Pierre Ricadat
Pierre Ricadat@ghostdogpr·
@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.
English
1
0
0
33
Pierre Ricadat
Pierre Ricadat@ghostdogpr·
@novalevys AI definitely helps but I understand/trust all the code I ship =)
English
0
0
1
30
Pierre Ricadat
Pierre Ricadat@ghostdogpr·
I haven’t even publicly announced my 3rd library yet and I’m already working on the 4th 😅
English
2
0
16
601
Nicolas Rinaudo
Nicolas Rinaudo@NicolasRinaudo·
@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. 💣
English
1
0
2
81
Pierre Ricadat
Pierre Ricadat@ghostdogpr·
@guizmaii One’s about Protobuf/gRPC, the new idea is related to pure domain logic.
English
0
0
6
144
Pierre Ricadat
Pierre Ricadat@ghostdogpr·
@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!
English
1
0
8
433
Adam Hearn
Adam Hearn@adamhearn·
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?
Adam Hearn tweet media
Scala@scala_lang

Please take a quick 5‑minute survey on Scala adoption and usage. Results will impact Scala’s roadmap, libraries, and tooling. Help shape the future of Scala! Brought to you by VirtusLab and the Scala Center. Survey: virtuslab.typeform.com/ScalaSurvey2026

English
4
4
33
2.8K
blergh
blergh@wnwbbprv4p·
@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
English
4
0
2
189
Flavio Brasil
Flavio Brasil@fbrasisil·
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 🚀🚀🚀
English
4
0
37
6K
Jules Ivanic
Jules Ivanic@guizmaii·
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
English
2
2
25
755
Pierre Ricadat
Pierre Ricadat@ghostdogpr·
@Krever01 I replaced some Mirror-based inline validation with a macro which allowed better error messages, reduced bytecode and faster compilation. Felt great!
English
0
0
7
153
Pierre Ricadat
Pierre Ricadat@ghostdogpr·
Coding agents gifted me the power of writing Scala macros, I feel unstoppable.
English
2
1
22
1.3K