<html><body><p><font size="2" face="sans-serif">8th Workshop on Reactive and Event-based Languages and Systems (REBLS 2021)</font><br><font size="2" face="sans-serif">co-located with the SPLASH Conference</font><br><font size="2" face="sans-serif">hybrid Virtual and in person in Chicago, Illinois, USA</font><br><font size="2" face="sans-serif">Sun 17 - Fri 22 October 2021</font><br><font size="2" face="sans-serif">Website: </font><a href="https://2021.splashcon.org/home/rebls-2021"><font size="2" face="sans-serif">https://2021.splashcon.org/home/rebls-2021</font></a><br><br><font size="2" face="sans-serif">IMPORTANT DATES</font><br><br><font size="2" face="sans-serif">Submission Deadline: 15 Aug 2021 (there will be no extension this year)</font><br><font size="2" face="sans-serif">Author Notification: 6 Sep 2021</font><br><font size="2" face="sans-serif">Camera Ready Deadline: 13 Sep 2021</font><br><font size="2" face="sans-serif">SPLASH Conference: 17 - 22 Oct 2021</font><br><br><font size="2" face="sans-serif">INTRODUCTION</font><br><br><font size="2" face="sans-serif">Reactive programming and event-based programming are two closely related programming styles that are becoming more important with the ever increasing requirement for applications to run on the web or on mobile devices, and the advent of advanced High-Performance Computing (HPC) technology.</font><br><br><font size="2" face="sans-serif">A number of publications on middleware and language design -- so-called reactive and event-based languages and systems (REBLS) -- have already seen the light, but the field still raises several questions. For example, the interaction with mainstream language concepts is poorly understood, implementation technology is still lacking, and modularity mechanisms remain largely unexplored. Moreover, large applications are still to be developed, and, consequently, patterns and tools for developing large reactive applications are still in their infancy.</font><br><br><font size="2" face="sans-serif">This workshop will gather researchers in reactive and event-based languages and systems. The goal of the workshop is to exchange new technical research results and to better define the field by developing taxonomies and discussing overviews of the existing work.</font><br><br><font size="2" face="sans-serif">We welcome all submissions on reactive programming, functional reactive programming, and event- and aspect- oriented systems, including but not limited to:</font><br><br><font size="2" face="sans-serif">* Language design, implementation, runtime systems, program analysis, software metrics, patterns and benchmarks.</font><br><br><font size="2" face="sans-serif">* Formal models for reactive and event-based programming.</font><br><br><font size="2" face="sans-serif">* Study of the paradigm: interaction of reactive and event-based programming with existing language features such as object-oriented programming, pure functional programming, mutable state, concurrency.</font><br><br><font size="2" face="sans-serif">* Modularity and abstraction mechanisms in large systems.</font><br><br><font size="2" face="sans-serif">* Advanced event systems, event quantification, event composition, aspect-oriented programming for reactive applications.</font><br><br><font size="2" face="sans-serif">* Functional Reactive Programming (FRP), self-adjusting computation and incremental computing.</font><br><br><font size="2" face="sans-serif">* Synchronous languages, modeling and verification of real-time systems, safety-critical reactive and embedded systems.</font><br><br><font size="2" face="sans-serif">* Applications, case studies that show the efficacy of reactive programming.</font><br><br><font size="2" face="sans-serif">* Empirical studies that motivate further research in the field.</font><br><br><font size="2" face="sans-serif">* Patterns and best-practices.</font><br><br><font size="2" face="sans-serif">* Related fields, such as complex event processing, reactive data structures, view maintenance, constraint-based languages, and their integration with reactive programming.</font><br><br><font size="2" face="sans-serif">* Implementation technology, language runtimes, virtual machine support, compilers.</font><br><br><font size="2" face="sans-serif">* IDEs, Tools.</font><br><br><font size="2" face="sans-serif">The format of the workshop is that of a mini-conference where participants present their work. Because of the declarative nature of reactive programs, it is often hard to understand their semantics just by looking at the code. We therefore also encourage authors to use their slots for presenting their work based on live demos.</font><br><br><br><font size="2" face="sans-serif">SUBMISSIONS</font><br><br><font size="2" face="sans-serif">REBLS encourages submissions of two types of papers:</font><br><br><font size="2" face="sans-serif">* Full papers: papers that describe complete research results. These papers will be published in the ACM digital library.</font><br><br><font size="2" face="sans-serif">* In-progress papers: papers that have the potential of triggering an interesting discussion at the workshop or present new ideas that require further systematic investigation. These papers will not be published in the ACM digital library.</font><br><br><font size="2" face="sans-serif">Format:</font><br><br><font size="2" face="sans-serif">* Submissions should use the ACM SIGPLAN Conference acmart Format with the two-column, sigplan Subformat, 10 point font, using Biolinum as sans-serif font and Libertine as serif font. All submissions should be in PDF format. If you use LaTeX or Word, please use the ACM SIGPLAN acmart Templates.</font><br><br><font size="2" face="sans-serif"> The page </font><a href="http://www.sigplan.org/Resources/Author/#acmart-format"><font size="2" face="sans-serif">http://www.sigplan.org/Resources/Author/#acmart-format</font></a><font size="2" face="sans-serif"> contains instructions for authors, and a package that includes an example file acmart-sigplan.tex.</font><br><br><font size="2" face="sans-serif">* Authors are required to explicitly specify the type of paper in the submission (i.e., full paper, in-progress paper).</font><br><br><font size="2" face="sans-serif">* Full papers can be up to 12 pages in length, excluding references. In-progress papers can be up to 6 pages, excluding references.</font><br><br><font size="2" face="sans-serif">Instructions for the Authors:</font><br><br><font size="2" face="sans-serif">* Papers should be submitted through: </font><a href="https://rebls21.hotcrp.com/"><font size="2" face="sans-serif">https://rebls21.hotcrp.com/</font></a><br><br><font size="2" face="sans-serif">* For fairness reasons, all submitted papers should conform to the formatting instructions. Submissions that violate these instructions will be summarily rejected.</font><br><br><font size="2" face="sans-serif">* Program Committee members are allowed to submit papers, but their papers will be held to a higher standard.</font><br><br><font size="2" face="sans-serif">* All submissions are expected to comply with the ACM Policies for Authorship that are detailed at </font><a href="https://www.acm.org/publications/authors/information-for-authors"><font size="2" face="sans-serif">https://www.acm.org/publications/authors/information-for-authors</font></a><font size="2" face="sans-serif">.</font><br><br><font size="2" face="sans-serif">* Each submission must adhere to SIGPLAN’s republication policy, as explained on the web at </font><a href="http://www.sigplan.org/Resources/Policies/Republication"><font size="2" face="sans-serif">http://www.sigplan.org/Resources/Policies/Republication</font></a><font size="2" face="sans-serif">.</font><br><br><font size="2" face="sans-serif">PROGRAM COMMITTEE</font><br><br><font size="2" face="sans-serif">Louis Mandel (PC Chair; IBM Research)</font><br><br><font size="2" face="sans-serif">Patrick Bahr, IT University of Copenhagen</font><br><font size="2" face="sans-serif">Manuel Bärenz, sonnen eServices GmbH</font><br><font size="2" face="sans-serif">Guillaume Baudart, Inria</font><br><font size="2" face="sans-serif">Guerric Chupin, University of Nottingham</font><br><font size="2" face="sans-serif">Stephen A. Edwards, Columbia University</font><br><font size="2" face="sans-serif">Alan Jeffrey, Roblox</font><br><font size="2" face="sans-serif">Tetsuo Kamina, Oita University</font><br><font size="2" face="sans-serif">Yoshiki Ohshima, Croquet Studio</font><br><font size="2" face="sans-serif">Jorge Pérez, University of Groningen</font><br><font size="2" face="sans-serif">Marc Pouzet, École normale superieure</font><br><font size="2" face="sans-serif">Noemi Rodrigues, Pontifícia Universidade Católica do Rio de Janeiro</font><br><font size="2" face="sans-serif">Partha Roop, University of Auckland</font><br><font size="2" face="sans-serif">Mark Santoluzito, Barnard College</font><br><font size="2" face="sans-serif">Jonathan Thaler, University of Applied Sciences Vorarlberg</font><br><font size="2" face="sans-serif">Reinhard von Hanxleden, Kiel University</font><br><font size="2" face="sans-serif">Takuo Watanabe, Tokio Institute of Technology</font><br><font size="2" face="sans-serif">Pascal Weisenburger, University of St. Gallen</font><br><font size="2" face="sans-serif">Tian Zhao, University of Wisconsin-Milwaukee</font><br><br><font size="2" face="sans-serif">ORGANIZING COMMITTEE</font><br><br><font size="2" face="sans-serif">Guido Salvaneschi, TU Darmstadt, Germany</font><br><font size="2" face="sans-serif">Wolfgang De Meuter, Vrije Universiteit Brussel, Belgium</font><br><font size="2" face="sans-serif">Patrick Eugster, Universita della Svizzera Italiana, Switzerland</font><br><font size="2" face="sans-serif">Francisco Sant'Anna, Rio de Janeiro State University, Brazil</font><br><font size="2" face="sans-serif">Lukasz Ziarek, SUNY Buffalo, United States</font><BR>
<BR>
</body></html>