I propose that we can extend Mirrors to operations, and use the most natural DSL of all - plain trait definitions.

Can we derive endpoints from just a trait definition? One of Scala's strengths is domain modelling, and from a data definition, we can derive generic information in a Mirror, e.g. to generate type classes. For operations (such as endpoints) there is less support from metaprogramming, so we often create DSLs to describe them. I propose that we can extend Mirrors to operations, and use the most natural DSL of all - plain trait definitions.
Let's write a game in Scala Native, for Playdate!
Listen to a story of how we have dealt with 201 obstacles allowing us to run multithreaded programs natively!
In this talk, we will start with the basics, understanding what build caching is and why it can be a bit tricky to handle in real projects.
The talk explores the recursive structure of Diamond Architecture.
Join me for a fun and possibly opinionated talk about the state of Scala and other JVM languages.
I would like to go over the most relevant tools and changes that can improve your developer experience.