If you caught the article about Proteus but prefer a video format, check out @ghostdogpr's talk from Scalar 2026! 🍿 He shows how Proteus uses zio-blocks to bypass traditional Chimney/Protobuf boilerplate and speed up (slow down?) Scala compile times. youtube.com/watch?v=zTq9gdIm…

A few people have asked me recently about the AI-related tools and skills I use, so here it is 👇 I'd love to know what your setup looks like - what tools are you using day-to-day?

/grill-me is my most popular skill ever. I get 5-10 messages a day about how it’s changed people’s workflows for the better But… I’ve stopped using it for code. Here’s the improved version:

🚨 I’m done with zio-http After 3.11, no more new features from me on the 3.x line. Instead I’m going full speed on zio-http 4 completely rebuilt on ZIO Blocks Code is already moving into blocks Cleaner. Faster. Simpler The future is coming 🔥 Who’s hyped?

I'm proud of this.

What the hell

For all the curious Java developers out there, here is a quick look at how to use Scala 3 with Spring Boot. But as the author says: "I have to warn you: you'll actually fall in love with this language very quickly. It's really easy to use and makes so much more sense than #Java in a lot of ways." youtube.com/watch?v=eVV2UW-k…

Men … vad hände här nu då 🥲

Obs! Jörgen vill INTE att denna bild sprids - visst vill vi hjälpa honom att sprida det budskapet? Dela - dela - dela 🙏

Den här tweeten får inte spridas under några omständigheter. Tack.

Problems with error handling and exceptions, part N 1; is that a sensible way to categorise and implement error handling? * recoverable, "expected" errors. Fully typed, as an `Either[E, T]` or `Result<T, E>` or a checked exception * unrecoverable errors. This includes bugs, but also anything that should terminate the current "processing unit": respond with a 500 to an HTTP request, fail an incoming MQ message, or just terminate a CLI app. Unrecoverable errors would be untyped **on purpose** (unchecked exceptions / panics) - making implementing control flow basing on the specific error as hard as possible. If there's any control flow you want to do - use a typed error. Otherwise - you get an untyped error-blob, which you can log, and respond to the user with whatever format of internal error that is appropriate. But there are no actions dependent on the error type. Of course, unrecoverable errors at one level might become recoverable at a higher one - by catching them. But the only information then would be what's accessible at the point where the error is caught.

Scala 3.8.3 is out 🎉 Besides the ported optimizer, it features a local on/off coverage switch. 🔄

Go check out ZIO Blocks! It's a collection of independent libraries with zero or minimal dependencies. Despite the name, ZIO is not needed to use them. ☝️ github.com/zio/zio-blocks

I wanted to release Hearth 0.3.0 after Scala 3.3.8 is out, and Kindlings 0.1.0 after that. But overwhelmingly positive reception (and a horse head in my bed) convinced my to release them much earlier, so...

Lika galet som att påstå att personer med kippa är för folkmord.

Scala Plugin 2026.1 is out! Here's what's new: - Dev Containers and WSL support - Markdown support in Scaladoc - Faster project sync times - Next edit suggestions enabled by default - Configurable delay for compiler-based highlighting Read more here: blog.jetbrains.com/scala/202… (1/2)

Software horror: litellm PyPI supply chain attack. Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords. LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm. Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks. Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages. Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.

roadmap.sh/scala Scala Roadmap for learning is now officially published. It contains over 150 nodes with descriptions and links to learning materials. It's aimed at beginners but I'm sure many advanced developers can find there something for them as well. Please share😊

Rika människor, som Ulf Kristersson själv, fick tusentals kronor sänkt skatt i månaden.

Friskolor dränerar offentliga skolor genom att attrahera "billiga" elever, vilket tvingar kommuner att höja skolpengen för att klara av "dyra" elever. Friskolorna tar sedan del av den höjda skolpengen. Kommunerna har dessutom ansvaret, vilket är kostsamt. Systemet är trasigt.