IDE as Code: Reifying Language Protocols as First-Class Citizens

Jeanjean, Pierre; Combemale, Benôıt; Barais, Olivier

doi:10.1145/3452383.3452406

Cited by 3 publications

(4 citation statements)

References 11 publications

(19 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As it is impossible to predict every possible reaction and incorporate them into the generic protocol, the need for possible adaptations always remains. This issue also applies to the DAP and other language protocols, where domain-specific languages (DSLs) (Merino et al 2020;Prähofer et al 2013) offer unique constructs that are not supported in the generic protocol (Jeanjean et al 2021).…”

Section: Extensible Debugging Toolsmentioning

confidence: 99%

Extensible Tooling for Reactive Programming Based on Active Expressions.

Ramson,

Brand,

Lincke

et al. 2024

JOT

View full text Add to dashboard Cite

Reactive programming uses dedicated language concepts such as signals, data bindings, and constraints, so developers can better express behavior that is triggered by data changes and user interactions. As applications also contain aspects that cannot be easily expressed through reactive programming, reactive concepts are often integrated into more generally applicable imperative programming languages. Although such language integrations are readily available, working on reactive code with tools designed for imperative code is hard, because without dedicated tool support implementation details may leak unintentionally. There are special tools for reactive programming available, however, they are expensive to make.Further, a tool typically supports only a single language concept and cannot be applied to others even though they build on similar ideas. Consequently, control flow or data flow cannot be followed between concepts.We propose to leverage the commonalities found in reactive programming concepts to create reusable tool components for data gathering and visualization. To do so we create a toolset working on a generalization of reactive programming concepts, Active Expressions. By building upon the generic tool components, tool developers can create tool support for specific reactive concepts. Furthermore, multiple reactive concepts and their potentially complex interaction can be explored in one shared environment. We implemented the approach in the Lively4 Web-based JavaScript development environment using its Active Expression framework. Our toolset gathers relevant data about the reactive system and visualizes it using code annotations, an overview tree, an event timeline, and a dependency graph. We evaluate the reusability of this toolset by adapting it to two more concepts: signals, and implicit layer activation, known from context-oriented programming. We found that most of the functionality provided by the toolset can be reused, thus, reducing the implementation effort. Further, we show that multiple reactive concepts can be supported by the same common toolset. Programmers can use and debug multiple different reactive concepts simultaneously, without requiring new tools for each one. For future work, we believe our common toolset provides a starting point for researching the interplay between multiple reactive programming concepts.

show abstract

Section: Extensible Debugging Toolsmentioning

confidence: 99%

Extensible Tooling for Reactive Programming Based on Active Expressions.

Ramson,

Brand,

Lincke

et al. 2024

JOT

View full text Add to dashboard Cite

show abstract

“…Jeanjean et al [11] propose a vision where the features of IDEs are dynamically configured by the languages they are currently working with. LSP and DAP enable some level of configurability, especially through capabilities.…”

Section: Debug Adapter Protocolmentioning

confidence: 99%

On the Suitability of LSP and DAP for Domain-Specific Languages

Enet,

Bousse,

Tisi

et al. 2023

2023 ACM/IEEE International Conference on Model Driven Engineering Languages and Systems Companion (MODELS-C)

View full text Add to dashboard Cite

Domain-Specific Languages (DSLs) help manage the growing complexity of systems by facilitating their description and execution or simulation via tailored languages. A large part of the development costs of a DSL comes from building the associated tools it requires, such as an editor or a debugger. To reduce these costs, the Language Server Protocol (LSP) and Debug Adapter Protocol (DAP) enable the creation of generic tooling interfaces which rely on standardized services exposed by languages. However, as these protocols have been designed for General Purpose Languages (GPLs), their applicability to DSLs has no yet been extensively studied. In this paper, we analyze both LSP and DAP, with an emphasis regarding their relevance for the development of tooling for DSLs. We provide both a highlevel insight into these protocols, such as a dependency graph of their services, and a more fine-grained qualitative analysis of each service. We show that while some services defined by these two protocols can be provided by any DSL, others make strong assumptions on the concepts that should be part of the considered DSL. Conversely, domain-specific concepts available in some DSLs are not exploitable through these protocols, thus reducing the capabilities of generic tools.

show abstract

“…However, these IDEs allow the installation of modules which provide Language Services, for instance the syntax highlighting of C programs or the debugging of Java programs. The trend of modularity in IDEs is very noticeable if we look at the 2019 Stack Overflow's annual Developer Survey 8 . According to this survey, the majority of the most popular IDEs (8 out of 10), such as Visual Studio Code or IntelliJ 9 , heavily rely on a plug-in mechanism to customize the environment according to the needs of the users.…”

Section: Motivationmentioning

confidence: 99%

“…In this article, we use the neologism microservicization, as in[8], to designate the transition process from monolithic to microservice architecture.3 https://www.eclipse.org/sirius/sirius-web.html…”

mentioning

confidence: 99%

From Monolithic to Microservice Architecture: The Case of Extensible and Domain-Specific IDEs

Belafia

Jeanjean

Barais

et al. 2021

2021 ACM/IEEE International Conference on Model Driven Engineering Languages and Systems Companion (MODELS-C)

Self Cite

View full text Add to dashboard Cite

HAL is a multi-disciplinary open access archive for the deposit and dissemination of scientific research documents, whether they are published or not. The documents may come from teaching and research institutions in France or abroad, or from public or private research centers. L'archive ouverte pluridisciplinaire HAL, est destinée au dépôt et à la diffusion de documents scientifiques de niveau recherche, publiés ou non, émanant des établissements d'enseignement et de recherche français ou étrangers, des laboratoires publics ou privés.

show abstract

IDE as Code: Reifying Language Protocols as First-Class Citizens

Cited by 3 publications

References 11 publications

Extensible Tooling for Reactive Programming Based on Active Expressions.

Extensible Tooling for Reactive Programming Based on Active Expressions.

On the Suitability of LSP and DAP for Domain-Specific Languages

From Monolithic to Microservice Architecture: The Case of Extensible and Domain-Specific IDEs

Contact Info

Product

Resources

About