Object-oriented Reactive Programming is Not Reactive Object-oriented Programming

Research output: Chapter in Book/Report/Conference proceedingMeeting abstract (Book)

Abstract

According to chapter 3 of Abelson & Sussman, there are two fundamentally different ways to organise large systems: according to the objects that live in the system, or according to the streams of values that flow through the system. Even though the notions of "object'' and "stream'' have meanwhile taken many incarnations, the dichotomy still exists in modern programming languages.
Marrying reactive programming and OOP is a research endeavour to come up with a unified model that embraces both styles of thinking. We identify two opposing research tracks towards the marriage. Existing work focuses on OO reactive programming, i.e. it uses object technology to compose reactions. Our work explores the converse: in the paper, we present the ROAM (Reactive Objects in AmbientTalk) model which is an experimental framework that explores objects as streams of reactive state.
Original languageEnglish
Title of host publicationREM 2013: Workshop on Reactivity, Events and Modularity
Number of pages5
Publication statusPublished - 28 Oct 2013
EventREM 2013 - Workshop on Reactivity, Events and Modularity - Indianapolis, United States
Duration: 28 Oct 201328 Oct 2013

Workshop

WorkshopREM 2013 - Workshop on Reactivity, Events and Modularity
CountryUnited States
CityIndianapolis
Period28/10/1328/10/13

Keywords

  • object-oriented programming
  • reactive programming
  • language abstraction

Fingerprint

Dive into the research topics of 'Object-oriented Reactive Programming is Not Reactive Object-oriented Programming'. Together they form a unique fingerprint.

Cite this