Design of an empirical study for comparing the usability of concurrent programming languages

Nanz, Sebastian; Torshizi, Faraz; Pedroni, Michela; Meyer, Bertrand

doi:10.1016/j.infsof.2012.08.013

Cited by 13 publications

(4 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Empirical evidence supports the claim that SCOOP indeed simplifies reasoning about concurrent programs as opposed to more established models (Nanz et al, 2011). The advantages of the model are due to a runtime system that automatically takes care of operations such as obtaining and releasing locks, without the need for explicit program statements.…”

Section: Introductionmentioning

confidence: 61%

Performance analysis of SCOOP programs

Morandi

Nanz

Meyer

2012

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

To support developers in writing reliable and efficient concurrent programs, novel concurrent programming abstractions have been proposed in recent years. Programming with such abstractions requires new analysis tools because the execution semantics often differs considerably from established models. We present a performance analyzer that is based on new metrics for programs written in SCOOP, an object-oriented programming model for concurrency. We discuss how the metrics can be used to discover performance issues, and we use the tool to optimize a concurrent robotic control software.

show abstract

Section: Introductionmentioning

confidence: 61%

Performance analysis of SCOOP programs

Morandi

Nanz

Meyer

2012

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

show abstract

“…They are controlled user studies that aim to determine the productivity of programmers. Nanz et al [21] compare two object-oriented languages, multi-threaded Java and SCOOP, for concurrent programming. Besides productivity, the comparison also focuses on the correctness of the programs written by the participants.…”

Section: Related Workmentioning

confidence: 99%

Why Do Scala Developers Mix the Actor Model with other Concurrency Models?

Tasharofi

Dinges

Johnson

2013

ECOOP 2013 – Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. Mixing the actor model with other concurrency models in a single program can break the actor abstraction. This increases the chance of creating deadlocks and data races-two mistakes that are hard to make with actors. Furthermore, it prevents the use of many advanced testing, modeling, and verification tools for actors, as these require pure actor programs. This study is the first to point out the phenomenon of mixing concurrency models by Scala developers and to systematically identify the factors leading to it. We studied 15 large, mature, and actively maintained actor programs written in Scala and found that 80% of them mix the actor model with another concurrency model. Consequently, a large part of real-world actor programs does not use actors to their fullest advantage. Inspection of the programs and discussion with the developers reveal two reasons for mixing that can be influenced by researchers and library-builders: weaknesses in the actor library implementations, and shortcomings of the actor model itself.

show abstract

“…There evaluations of programming languages for non-programmers such as [6], [7], and [8]. Then there are empirical evaluations of other programming languages for novice programmers such as [9], [10], [11], and [12]. Moreover, there is a comparison between Android and iOS, an professional programming language which is similar to Android, in teaching environment [13].…”

Section: Reusing Android Apps Between Tasksmentioning

confidence: 99%

“…Nanz, Torshizi, Pedroni, and Meyer [11] do experiment on 67 students of an architecture course to compare Java with SCOOP (Simple Concurrent Object-Oriented Programming) for concurrency. The experiment includes two phrases: (1) training phase, including self-study material and exercises, to help students be familiar with concurrent programming in both languages, (2) testing, including three tasks program comprehension, program debugging and program correctness, to evaluate the usability of Java and SCOOP.…”

Section: Empirical Evaluations Of Programming Languages For Novice Prmentioning

confidence: 99%