Optimizing an IDE for an Evolving Language Ecosystem
Fuente:
arXiv
Enregistré dans:
| Auteurs principaux: | , , , , |
|---|---|
| Format: | Preprint |
| Publié: |
2026
|
| Sujets: | |
| Accès en ligne: | |
| Tags: |
Ajouter un tag
Pas de tags, Soyez le premier à ajouter un tag!
|
| _version_ | 1866914571565924352 |
|---|---|
| author | Welc, Adam Nowacki, Todd Russi, Dario Swords, Cameron Zakian, Timothy A. K. |
| author_facet | Welc, Adam Nowacki, Todd Russi, Dario Swords, Cameron Zakian, Timothy A. K. |
| contents | This paper describes a strategy for developing a high performance and feature-rich IDE for an evolving smart contract language ecosystem. Our target is Move, a programming language for the Sui smart contracts platform. The strategy we chose to support the Move language ecosystem utilizes Language Server Protocol (LSP) and it is based on the already existing "core" language machinery, in particular the core language compiler. We discuss alternatives we considered, as well as the evolution of our infrastructure that was necessary to keep up with the growth of the language ecosystem, particularly with respect to optimizations (and their impact) that needed to be implemented to accommodate this growth. We conclude with lessons learned during the IDE support development process that we hope will be beneficial for others attempting to follow a similar path. |
| format | Preprint |
| id |
arxiv_https___arxiv_org_abs_2605_16664 |
| institution | arXiv |
| publishDate | 2026 |
| record_format | arxiv |
| spellingShingle | Optimizing an IDE for an Evolving Language Ecosystem Welc, Adam Nowacki, Todd Russi, Dario Swords, Cameron Zakian, Timothy A. K. Software Engineering This paper describes a strategy for developing a high performance and feature-rich IDE for an evolving smart contract language ecosystem. Our target is Move, a programming language for the Sui smart contracts platform. The strategy we chose to support the Move language ecosystem utilizes Language Server Protocol (LSP) and it is based on the already existing "core" language machinery, in particular the core language compiler. We discuss alternatives we considered, as well as the evolution of our infrastructure that was necessary to keep up with the growth of the language ecosystem, particularly with respect to optimizations (and their impact) that needed to be implemented to accommodate this growth. We conclude with lessons learned during the IDE support development process that we hope will be beneficial for others attempting to follow a similar path. |
| title | Optimizing an IDE for an Evolving Language Ecosystem |
| topic | Software Engineering |
| url | https://arxiv.org/abs/2605.16664 |