Rethinking the debugger: the Future (is) in reactive applications
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:
- Lightbend Scala Language - Professional (in London on 9th - 10th September 2019)
- Lightning Talk - 5 Things You Need to Know About Scala Compilation: #3 Will Blow Your Mind! (SkillsCast recorded in December 2017)
- Fast Track to F# with Tomas Petricek & Phil Trelford (in London on 9th - 10th September 2019)
- Scala eXchange London 2019 (in London on 12th - 13th December 2019)
- Workshop: Improving compile times (in London on 23rd July 2019)
- London Java Community July (in London on 24th July 2019)
- Why API Design Matters, and Why Yours Sucks! (and mine sucks too!) (SkillsCast recorded in June 2019)
- The Elements of Tagless Final Style (SkillsCast recorded in May 2019)
Thanks to our sponsors
Rethinking the debugger: the Future (is) in reactive applications
Iulian Dragos
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.
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:
- Lightbend Scala Language - Professional (in London on 9th - 10th September 2019)
- Lightning Talk - 5 Things You Need to Know About Scala Compilation: #3 Will Blow Your Mind! (SkillsCast recorded in December 2017)
- Fast Track to F# with Tomas Petricek & Phil Trelford (in London on 9th - 10th September 2019)
- Scala eXchange London 2019 (in London on 12th - 13th December 2019)
- Workshop: Improving compile times (in London on 23rd July 2019)
- London Java Community July (in London on 24th July 2019)
- Why API Design Matters, and Why Yours Sucks! (and mine sucks too!) (SkillsCast recorded in June 2019)
- The Elements of Tagless Final Style (SkillsCast recorded in May 2019)
Thanks to our sponsors
Rethinking the debugger: the Future (is) in reactive applications
Iulian Dragos
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.