Please log in to watch this conference skillscast.
Futures, actors or iteratees make code easier to write and reason about, and in this talk I'll show a simple solution to make them easier to debug. The tool I present integrates well with the Eclipse plugin for Scala, and shows how a "reactive debugger" might look like.
New abstractions for concurrency make writing programs easier by moving away from threads and locks, but debugging such programs becomes harder. The call-stack, an essential tool in understanding why and how control flow reached a certain point in the program, loses meaning when inspected in traditional debuggers.
YOU MAY ALSO LIKE:
- Lightning Talk - 5 Things You Need to Know About Scala Compilation: #3 Will Blow Your Mind! (SkillsCast recorded in December 2017)
- Functional Concurrency in .NET with C# and F# with Riccardo Terrell (Online Course on 8th - 11th March 2021)
- Extreme Java: Concurrency Performance with Dr Heinz Kabutz (Online Course on 31st March - 2nd April 2021)
- Concurrency in Crystal (SkillsCast recorded in October 2019)
- Abstract Data Types In The Region Of Abysmal Pain, And How To Navigate Them (SkillsCast recorded in September 2019)
Rethinking the debugger: the Future (is) in reactive applications
Iulian Dragoș dreams about a world where the Scala programming language is the default choice for new projects. He learned Scala by writing the compiler backend for it during his PhD at EPFL, back in 2004, and he was the first employee of Lightbend (formerly Typesafe). At Lightbend he helped the company grow from 5 to 85 employees, playing the role of engineer, technical lead, consultant, trainer or sales engineer. Iulian is a frequent speaker at conferences and actively contributing to several open-source projects.