InfoQ Homepage Presentations The Next 700 Asynchronous Programming Models
The Next 700 Asynchronous Programming Models
Summary
Philipp Haller explains how to make Rx programming more natural and intuitive by generalizing Scala's Async which, so far, has been used to program with non-blocking futures in a familiar direct style
Bio
Philipp Haller is a Consultant at Typesafe and a member of the Scala team. He created Scala's first actors library, and is one of the lead designers of the futures library of Scala 2.10. He worked on parallel domain-specific languages embedded in Scala at Stanford's Pervasive Parallelism Lab and co-authored the book “Actors in Scala”.
About the conference
SPLASH is home to OOPSLA, Onward! and DLS. OOPSLA is the forum for many important software developments of the last few decades: CRC cards, CLOS, design patterns, Agile, SOA, Wikis, UML, TDD, refactoring, Java, and Aspects. Onward! is about programming and software: processes, methods, languages, communities, and applications. DLS addresses dynamic languages: their implementation and application.
Community comments
async challenge
by Ben Mabey,
rasync vs rx, personal opinion
by Alexander Semenov,
async challenge
by Ben Mabey,
Your message is awaiting moderation. Thank you for participating in the discussion.
I implemented the challenge in the talk with CSP (using clojure) without any of the helper fns (combinators) to see how it would compare to the rasync version:
gist.github.com/bmabey/9356141
rasync vs rx, personal opinion
by Alexander Semenov,
Your message is awaiting moderation. Thank you for participating in the discussion.
Personally, I found rasync version much harder to get. It introduces mutable variables and forces you to write code in Java (not Scala) style, non-functionally.