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:
- Functional Concurrency in .NET with C# & F# with Riccardo Terrell (in London on 20th - 21st September 2018)
- Lightbend Akka for Scala - Professional (in London on 25th - 26th October 2018)
- Lightbend Akka for Scala - Expert (in London on 26th - 27th November 2018)
- ScalaX2gether Community Day 2018 (in London on 15th December 2018)
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.
-
SkillsCast
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:
- Functional Concurrency in .NET with C# & F# with Riccardo Terrell (in London on 20th - 21st September 2018)
- Lightbend Akka for Scala - Professional (in London on 25th - 26th October 2018)
- Lightbend Akka for Scala - Expert (in London on 26th - 27th November 2018)
- ScalaX2gether Community Day 2018 (in London on 15th December 2018)
Thanks to our sponsors
-
About the Speaker
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.