Textual and Graphical Languages for the Cloud Era
summary
Demonstrates a working cloud IDE stack that originally mixes Xtext + LSP4J (Java) back end with Theia and Sprotty front end, showing one concrete result: a state-machine DSL with live text/diagram sync that supports rename refactoring, validation, code generation and side-by-side editing. Argues that the mixed Java/TypeScript setup incurs high maintenance and proposes Langium (TypeScript-only) as a drop-in alternative using Chevrotain parsing, Monaco editor and web-worker language servers so the same language runs in browser, Node CLI or VS Code.
AI-written summary · about
chapters (15)
- 0:00DSLs in the cloud
- 3:17Original architecture review
- 8:38Mixed tool stack challenges
- 11:07Langium as solution
- 17:31Langium with Sprotty
- 19:39Live demo new setup
- 21:49DSLs in browser
- 24:40Consistent tech stack
- 26:27Getting started Langium
- 27:12Langium type checking future
- 29:08Parser details
- 31:36Multi-user editing
- 33:42Text vs graphics input
- 34:50Migration paths
- 36:55Q&A
related talks
30mDomain-Specific Languages in the Cloud
26mDSLs in the cloud with Langium and Theia
32mBuilding cloud-native (modeling) tools
06mZero to One How to Integrate a Graphical Editor in a Cloud IDE
34mBuilding Web-based Modeling Tools based on Eclipse Theia
25mWeb-based Tools and IDEs: Accomplishments and Opportunities
29mIntegrating Language Engineering into the Software Development Process
27mHow browser IDEs are enabling the transition of development to the cloud