fpjos

YouTube video by Martin Kleppmann Distributed Systems 6.2: Raft

📺 "Distributed Systems 6.2: Raft"

Enjoyed this intro to the Raft consensus algorithm, part of a larger DistSys lecture series by @martin.kleppmann.com. The pseudo-code makes it actually digestible really well. Great watch!

www.youtube.com/watch?v=uXEY...

i just released a new blog post (part 1 of 2) discussing the well-known paper "the ironies of automation" and what its findings mean for the current agentic ai automation move (spoiler: quite some questions we still need to find answers for). enjoy if you like ... ;)

www.ufried.com/blog/ironies...

Today, instead of announcing a new feature, we would like to ask you about a possible new one. 🔎

In some other languages, it's possible to evaluate inline with the `>>>` symbol in a comment. This gives you a quick ability to evaluate some code. Should we add it to Metals?

A language might be brilliant but community health is the most important factor to its survival/growth (see python, rust even java), and right now scala steering committee and Odersky does not care at all about it

more and more like this; to my great despair because I love the language and invested so much of my time in it. Still hoping things could improve so many great contributors who left would come back but I'm afraid it'll go the haskell way (extreme ivory tower syndrome).

scala if its community management was a true opened and welcoming meritocracy and not driven by politics

released a new blog post in the light of the recent aws outage, discussing why blaming aws is exhibiting outdated thinking patterns and what you need to do instead if you want to build reliable systems today: www.ufried.com/blog/it_is_y.... enjoy if you like ... ;)

I love the language which is beautiful and incredibly powerful, invested a lot on it, know how much better than anything else it is on the jvm... But I seriously ponder to move to other stacks (mainly ocaml and rust) where community steering seems much less ivory-tower inclined

Honest question: is there still a chance scala community steering will stop its self-destruction management soon ? (zio excluded, kyo excluded and now abandoned, key innovators and evangelists leaving, ...) Seriously, community is shrinking, innovation is leaving, commercial opportunity is vanishing

i released a new blog post discussing that using genai agents for coding – while impressive in their capabilities – primarily seem to be a technological distraction from underlying, deeper problems (again): www.ufried.com/blog/ai_assi.... enjoy if you like ... ;)

page not found

released scalaxb 1.12.4
scalaxb.org/scalaxb-1.12.4 #Scala

same here, maybe it's unfamiliarity, time will tell, but I find kyo effect system easier to understand and to read

released scalaxb 1.12.3 featuring
- sbt plugin cross built to sbt 1.x and 2.x
- fixes Dispatch 2.x support
- updates to Log4j 2.x
scalaxb.org/scalaxb-1.12.3 #Scala

GitHub - softwaremill/realworld-tapir-zio: RealWorld.io with tapir and ZIO RealWorld.io with tapir and ZIO. Contribute to softwaremill/realworld-tapir-zio development by creating an account on GitHub.

ZIO+Tapir+Quill combo template with CRUD operations, authentication, routing, pagination, monitoring and more. AKA type-safe, purely functional alternative to the Spring Boot ecosystem. #scala #zio github.com/softwaremill...

Guido van Rossum acted as a wise leader, welcoming a truly diverse community. Does scala leadership? Currently this is not the impression it gives. Continue to deny the discomfort would be a grim and fatal answer. Up to you Mr Odersky, choose a direction so we can decide our fate

Comparing python vs scala community steering : one is incredibly successful, the other 'not so much'. Python also had to overcome similar challenges (eg: v2 to v3). Scala Center should take some inspiration from them.

Langton, Degoes, Brasil are also taking some distance. Sectarian behavior from Scala Center actively boycotting ZIO&KYO (fear of concurrents, maybe just childish behavior ?) is so unhealthy. They act in a self destructive manner & in the same time would deny any problems. When will this change ?

And I think M. Odersky has a huge responsibility on what's happening to the community right now

Utterly disgusted by Scala Center people and toxic 'culture' : they are so 'welcoming' and 'successful' that they push Kit Langton, John Degoes (ZIO) or Flavio Brasil (KYO) and many other to leave or take distance from scala. I'm so disgusted right now. They are actively killing Scala

GitHub - seroperson/zio-http-pac4j: zio-http wrapper for pac4j, security framework to protect your web applications zio-http wrapper for pac4j, security framework to protect your web applications - seroperson/zio-http-pac4j

I want to introduce to you my very recent library: zio-http wrapper for pac4j. pac4j is an easy and powerful security framework for authenticating users, getting their profiles, and managing authorizations to secure web applications and services.

github.com/seroperson/z...

#scala #zio #pac4j

To support the very first zio-http-pac4j release, I also wrote an article:

🔍 seroperson.me/2025/09/03/z...

It shows in details how to implement a JWT-based authorization for zio-http and also covers such features as token expiration, encryption, roles and custom payload.

#scala #zio #jwt #pac4j

I believe that regarding the deep fractures in the scala community no one can say Scala Center demonstrated a successful leadership (to say the least) and we're now in really serious danger zone. Hope people in charge will overcome denial and change direction for the best

Unison for Scala devs · Unison programming language

Very nice side-by-side #Unison - #Scala language guide

www.unison-lang.org/compare-lang...

@unison-lang.org

IntelliJ 2025.2 with the Scala Plugin is out! 🎉 Some of the new features include:
- support for named context bounds, e.g., def reduce[A: Monoid as m](xs: List[A]): A
- highlighting for duplicated field names in a named tuple
- support for referenceable package objects
#scala

i released the 5th and last post of my series that reflects upon (purely) AI-agent-based software development, containing a summary from a different angle, recommendations how to hedge options as developers and some final thoughts in general: www.ufried.com/blog/ai_and_...

enjoy if you like ... ;)

GitHub - com-lihaoyi/utest: A simple testing framework for Scala A simple testing framework for Scala. Contribute to com-lihaoyi/utest development by creating an account on GitHub.

Version 0.9.0 of the uTest #Scala testing framework is out, now with pretty-printed logging, diffs, and auto-updating golden-tests! github.com/com-lihaoyi/...

Release Kyo 1.0-RC1: A New Era of Simplicity and Stability · getkyo/kyo · GitHub We're excited to announce that Kyo is finally entering a period of API stabilization! 🚀 Over the past three years, we've quickly iterated on the abstractions of the library to ensure they're reliab...

The release candidate of Kyo 1.0 is a huge success, and as Flavio wrote, it's a significant evolutionary step in Scala. But remember, based on the last survey, only about 30% of commercial projects have migrated to Scala 3 😬 #scala github.com/getkyo/kyo/r...