@[email protected] 🔸️ Marcin Szałomski

@PiotrRaszkowski What did you use for voice recognition? For example, the MS Teams meeting transcription feature is terrible, and I would be more than afraid of turning it into requirements.

🎙️ Our client recorded two voice notes with his product vision. 20 min, stream of consciousness, in Polish. We turned that into: - transcripts - 21-section vision doc - 10-slide presentation - 9 epics + 10 GitHub issues with acceptance criteria No workshop. Just talking. #AI

@riccardo_cardin I think the way Sttp is implemented is convenient for lifting. Let's see. Tapir (on top of Sttp) supports Loom.

@baldram Hey, thanks 🙏. I'll check it for the next round. The hard part is to lift the external libraries' features to the virtual threads machinery

Today it's Father's Day in Italy! 🇮🇹 What better event for a new version of #YAES? Version 0.16.0 is out, and we introduced HTTP Client! It's a wrapper around #Java HttpClient, but lifted to effect tracking 🚀 Plus, we reinvented the site: blog.rcard.in/yaes/ #Scala devs, check it out, and see you at the @scalarconf next week! 💖 Here are the release notes: github.com/rcardin/yaes/r… cc @petr_zapletal

@riccardo_cardin Example: Don't want to use Circe since already use Jsoniter, so won't use Yaes since it has unwanted dependencies. Sttp solves it. It's loosely coupled, so can use whatever JSON lib as well as an HTTP client. The Java HTTP client is the default one, but I can swap it if needed.

@riccardo_cardin Yaes grows and grows to little ecosystem. Congrats! Have you considered Sttp interoperability? It brings a lot of features and flexibility that it might be a challenge to compete. Also it's a standard, as Sttp is part of Scala Toolkit. docs.scala-lang.org/toolkit/introd…

@matej_cerny So, you're saying I'll see different stacktraces compared to what I get with log4j? We thought about Scribe, but since we use log4j for so many Java libs anyway, we didn't want to add another logger. Sadly log4j is also one of the reasons for slow cold starts (classloaders).

Scribe gives you detailed method and line number logging with absolute zero runtime cost. How?

Who gets excited about a logging framework? You will when you see these benchmarks. 👇

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…

@matej_cerny This is a true pain point. On the other hand, the way Sttp is implemented is quite inspiring, with a common implementation and kinda adapters. I would only use the "TF for humans" style by Noel Welsh if possible.

I'm currently working on a tiny library and the truth is, that at least 90 % of the code are bridges to a different json codecs and db backends. And I haven't even started with the ZIO interop 🤷

@PiotrRaszkowski Nikt? Gdzie to AI, które miało nas oddelegować na becha? ;-)

Smutna opinia... ale #OpenClaw wydaje się, że jest martwy. Ten projekt ma 5k+ issues i 5k+ PRs... nikt... powtarzam... nikt nie jest w stanie tego ogarnąć, a do tego autor poszedł sobie pracować do Sama.

@kitlangton @opencode Looks smooth as Laminar, isn't it? ;-)

Now in @opencode desktop.

@matej_cerny @bilal_fazlani @openclaw Whoa, they made an even more performant one 🤯

@bilal_fazlani @baldram @openclaw Here it is x.com/i/status/20245…

I tried @openclaw and I am loving it ♥️ 🦞 Can't go back to not using it

@matej_cerny @bilal_fazlani @openclaw I'm looking at github.com/zeroclaw-labs/…. Probably will have less ready to use integrations, but I'm software engineer :)

@bilal_fazlani @baldram @openclaw I heard that there are several more secure clones now...

@matej_cerny Complainers gonna complain! 🤷‍♀️ We've successfully migrated dozens of microservices, even large ones, with minimal fuss – sometimes it was even automatic!

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.

Let's help the #Scala team make the language even better! Being around #Bazel events, I've heard a lot about Scala (support for Scala wasn't perfect in the past), and this is exactly the voice that the @scala_lang team needs. It took me just ~5 minutes to fill it up.

Side-effect handling is a pain point in every functional programming language. In #Scala, we can choose between different approaches. Everyone has pros and cons. Let's see what an Effect System is, what is currently available, and what the difference is between monadic (Cats Effect, ZIO, Kyo) and direct style (#YAES and Ox). No prior bias, I promise 😇

@jdegoes The Native variant is not mentioned. Does it mean that there's bo plan to support it?

When DI wiring fails, ZIO Blocks Scope gives you rich error messages with actionable hints to fix the problem. Scala 2.13 + 3, JVM + Scala.js, zero deps.

Scope in ZIO Blocks now has obvious overlap with both Ox (Scope/resources) and MacWire. How do the two stack up? 🤜🤛👀 👇🧵

@jdegoes So much important today for an LLM Agent to enable them fix an issue efficiently.

@ChShersh If it starts with April = 1, it would be correct.

I've just seen the worst enum in my life

What would you call a Scala library that: • Makes resource leaks a compile error, not a runtime bug • Auto-wires your entire DI graph from constructors • Almost no runtime overhead How about: Scope, in ZIO Blocks. Zero deps—works with ZIO, Cats, Kyo, or plain Scala. 👇

@Krever01 [2/2] ..but exploring alternatives. Will use LLMs, but not everything needs AI - many cases work w/ decision rules. Workflows4s might hit Lambda's 15min timeout, though Lambda Durable Functions could help 🤔 Will be evaluating architectural fit.

@Krever01 [1/2] In Q2 I'll be evaluating workflow options, so workflow4s. Since there's decision logic involved, decisions4s might also be useful. Main requirement: must work well in serverless environments. StepFunctions is obviously being considered, but ...

I would really like to increase decisions4s adoption. What would it take for you to use it? (Answer in replies) Which of the below best describes your codebase?