Tooling for the JavaScript Era
summary
Team prototypes a lightweight browser editor called Scripted that pulls the Eclipse Orion editor component into a local Node server, adds JS‑lint, Esprima-based recoverable parsing, dependency analysis and AMD/RequireJS module awareness, and ships the code on GitHub. Demo shows instant startup, editor content assist driven by JSDoc type hints, and an exec key that runs vmc push to Cloud Foundry so edits deploy live. Worked well enough for feedback; earlier full cloud workspace Orion prototype failed because users reject moving sources off their machine.
AI-written summary · about
chapters (8)
- 0:00Introduction and team
- 3:53Why JavaScript tooling
- 9:10Prototyping approach
- 19:08First prototype failure
- 28:48Scripted editor prototype
- 1:01:54Demo of Scripted editor
- 1:15:57Future of Scripted
- 1:28:15Q&A
related talks
20mOrion: The web is my development environment
26mOnline web application editor
34mKick ass code editing and end to end JavaScript debugging
35mBuilding a Browser Based Code Editor
05mBuilding Editors in the Browser
34mTowards a simpler JavaScript ecosystem
34mBuilding a Browser Based Code Editor
25mElectron: Desktop Apps with JavaScript