The milestone v1.0.0 release of the zio-spark wrapper has landed! 🎉 Featuring a major migration to Spark 4. github.com/guizmaii-ope... #scala
04.03.2026 15:05
👍 1
🔁 1
💬 0
📌 0
The milestone v1.0.0 release of the zio-spark wrapper has landed! 🎉 Featuring a major migration to Spark 4. github.com/guizmaii-ope... #scala
i released a new blog post discussing why you are not "left behind" if you do not become an AI-based software development expert right now, but still need to learn AI-based software development. sounds paradoxical? yes, the world sometimes is ;)
enjoy if you like ;)
www.ufried.com/blog/not_lef...
⛄ released sbt 1.12.4, featuring
- an `sbt` runner script bug fix
- a `scalaOrganization` bug fix
eed3si9n.com/sbt-1.12.4 #Scala
Micro-library exposing an API for "delimited-continuations" for #Scala JVM, ScalaJS and Scala Native. Extracted from "lampepfl/gears", may be useful for "direct style" libraries that want to be cross-platform.
github.com/funfix/con...
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/ScalaSurvey...
I released a new blog post, discussing the concept of "technical debt", how it is about much more than technical debt alone, what we actually try to achieve – resulting in an extensive graph of detrimental drivers we need to consider. enjoy if you like ... ;)
www.ufried.com/blog/forget_...
If you ever wanted to easily program on GPU with Scala in a functional way, your wait is over! Read more about on cyfra.computenode.io/
1) Software engineering is not about building features
2) Refactoring is a business problem
3) Software engineering is not an engineering practice
4) LLMs will not replace software engineers
5) Architects don't make decisions
by @swardley.bsky.social & @tudorgirba.com
medium.com/feenk/rewild...
In Czech, Chanterelle 🍄 is called "the fox". 🦊 In Scala 3, it means easy named tuple manipulation. A handy utility library from the author of ducktape. #scala github.com/arainko/chan...
📺 "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
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
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
