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 https://t.co/htxLQ6iHwH 🙏
Rehauled my /refine skill around this old quote from @guizmaii
Agents are very good at the "make it work" part. The skill takes it to another level by doing multiple passes on "make it correct, make it elegant, make it fast".
https://t.co/UkuWqfnMaE
@matej_cerny Yeah decided to upgrade as well. Only in Caliban I’m waiting because there’s a sbt plugin and sbt 2.0 needs 3.8. I’ll upgrade once there’s sbt 2.1 final
Released a new version of Sage with:
- a new testkit module that gives you an in-memory SageClient that doesn't require a real Redis/Valkey to work
- support for RESP2 for use with older Redis or particular configurations where RESP3 is not supported (e.g. Tencent Cloud)
Shardcake is now Shard! Yes, I dropped the "cake". As I left Devsisters in August, I forked the project and gave it a second life and a new home: https://t.co/dxCnbSWhSC
I just released a first RC with a new typed API, the ability to use Protobuf instead of Kryo, and a lot more!
@riccardo_cardin@eezoframework I don’t have a particular plan but I noticed using it from Eezo wasn’t very friendly as it was forcing using Ox for anything direct style, even though the underlying implementation has no such constraints.
I added a new direct-style, dependency-free, blocking backend to my Redis/Valkey library for Scala, Sage. The goal was to make it usable easily from the new @eezoframework
Reminder that Sage offers first-class support for absolutely all Scala stacks!
I applied an idea from @fwbrasil to create my own "refine" skill that reduces code complexity (and size) using an orchestrator agent and 3 subagents iterating on Constraints (Bjarnason), Simplicity (Hickey) and Parametricity (Wadler). Produced design and code looks much better!
Constraints: what freedom can we remove so fewer incorrect implementations are possible?
Simplicity: which independent concerns have become entangled?
Parametricity: what does the type actually guarantee, and what still depends on implementation discipline?
Introducing Caliban Gateway, a new module to combine remote Apollo Federation subgraphs, plain GraphQL services and local Caliban APIs into a single graph.
This has been in the works for more than 3 years, and I am glad to finally release a first version in Caliban 3.2.0. As usual, UX should be quite nice and performance is very competitive 🚀
Give it a try and let me know what you think 🙏
More details here: https://t.co/GWJVr4ZfhZ
Released a new version of Sage (my Redis/Valkey Scala client) with an easy to use distributed lock feature.
Ideal for cases where you want to prevent something running concurrently across multiple servers and don't want to reach for distributed actors or other more complex solutions (e.g. low contention, order doesn't matter).
Also upgraded Scala version to the new LTS (3.9.0).