Adam Warski
I am one of the co-founders of SoftwareMill, where I code mainly using Scala and other interesting technologies. I am involved in open-source projects, such as sttp, tapir, Quicklens, ElasticMQ and others. I have been a speaker at major conferences, such as JavaOne, LambdaConf, Devoxx and ScalaDays.

Apart from writing closed- and open-source software, in my free time I try to read the Internet on various (functional) programming-related subjects. Any ideas or insights usually end up with a blog.

LOCATION: Zürich
KEYWORDS: Concept, Language, Open Source

SPEAKER: Adam Warski   COMPANY: SoftwareMill
SLIDES: 230516_effects.pdf

Static typing is hardly controversial, but how far should we push the type system? What information should the types include, and what properties should they prove?

That’s where effect systems come in, but unlike the general approach, their answers to the questions above are hot debate topics!

Navigating the design space isn’t easy. Before we make up our minds, more questions need answering first: why do we need an effect system at all? How do effect systems differ? What are their tradeoffs?

Looking at Java in particular - what’s the effect system that is already present in Java? Do virtual threads (Loom) have anything to do with effect systems?

Let’s explore the options in Java, Scala, and beyond.

LEVEL OF TALK: Intermediate
LANGUAGE: Talk: en / Slides: en

Adam Warski
I am one of the co-founders of SoftwareMill, where I code mainly using Scala and other interesting technologies. I am involved in open-source projects, such as sttp, tapir, Quicklens, ElasticMQ and others. I have been a speaker at major conferences, such as JavaOne, LambdaConf, Devoxx and ScalaDays.

Apart from writing closed- and open-source software, in my free time I try to read the Internet on various (functional) programming-related subjects. Any ideas or insights usually end up with a blog.

---