Hi, I'm happy to announce that I'm here to help your Scala team and Scala-based products succeed. I will be available for any questions, suggestions and complaints during my open hours that should start this week (TBA soon). PMs are open. I'm also available on Scala, Typelevel

Safe resource usage is coming to #Scala! Scala 3.8 is just around the corner (you can test 3.8.0-RC3) - it's a great occasion to try out capture checking. But first, you have to understand how it works - here's my attempt:

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?

I wrote a thing about a thing we did and continue doing. If infra and typed fp systems are your thing, this might be of interest to you.

I have huuuuge hopes for Hearth

This. With all the "useworkflow drama", just a reminder: workflows4s is the exact opposite of magic. It might not be as pretty but its relatively simple. We don't do magic in Scala (usually).

hahaha, right on point

If you aren't familiar with Tapir yet, here's a hello-world tutorial:

https://t.co/sVcokPdBNO

Besom 0.5 - @pulumicorp for Scala 3 is finally here! This is mainly a bugfix release focused on stability that solves almost all known issues and brings us very close to 1.0.0. New features available in this release are: * `withArgs` - a copy method for input classes that

The first release is done, better macros are possible https://t.co/LGcZf0akNY

Wasm 3.0 is completed, with major new features like GC and exception handling! Scala is now acknowledged as a language that compiles to WebAssembly 🚀 https://t.co/yVvqrGuceL > With these new features, Wasm has much better support for compiling high-level programming languages.

This whole post was written as a reply to Flavio's post attached on screencap, who apparently unblocked me here on X only to post that and then blocked me again. I hope you can help me deliver the response to his feed. Why don't you tell the whole story Flavio? The story starts

This went well.

Scala 3.7.3 just dropped today! It adds one important lint - compiler now warns when given provided in scope is shadowed by default implicit argument. This might prevent some unexpected runtime bugs. See the example from announcement. https://t.co/WrOqcf4RjM Towards 3.8 now!

@lukasz_bialy @sudo_goreng @matej_cerny And I "made cross-compilation possible" not by reimplementing Scala 2 macros in Scala 3 macros, but by carefully selecting abstraction that could be implemented by both and which never have all features of either. You won't add some magic import which will make old macros compile

I'm going to go a step further here: if you have weird failures in Metals like silent crashes, weird mid-run stalls, functionalities that work and then suddenly stop to work - give as u shout! Talk with your legal, sign a NDA with us so that you can share your problems with

In Bootzooka - our direct-style #Scala service template - there's a single source of truth when it comes to HTTP endpoints: the code-first description in the backend. From that, during development, an `openapi.yaml` file is generated, after reach successful backend compilation.

Direct style: Scala's gamble, or simply continuing a consistent language design? https://t.co/F4N7j9eOtP

The promised link: https://t.co/qvSEh2XSrk

I value the Alex's opinion but I'd like to offer several additions, clarifications and/or counterpoints: 1. Realistically speaking gears not supporting scalajs platform is not a huge problem exactly because it will support wasm. Thus the only runtime where it could matter is the