The Future of Cloud Development is Editor Neutral
summary
Cloud IDE effort at coder.com builds a cloud IDE in 2018, fails as a full replacement and shuts down, then pivots to a lighter path by shipping code-server (a hacked VS Code web runtime around v1.36) and later supporting vs code remote, projector and plain SSH. Claim: editor neutrality is achievable by letting favorite editors connect to remote workspaces; surprising concrete win is burstable builds up to 96 cores and faster stack changes, and a practical roadmap to OS and stack neutrality.
AI-written summary · about
chapters (7)
- 0:00History of code editors
- 1:35Lessons from Coder IDE
- 2:58The emergence of code-server
- 4:43Principles of developer tools
- 6:45The future of cloud development
- 8:34Achieving editor neutrality
- 10:08Q&A and closing remarks
related talks
45mContaining Your Development – Why Cloud IDEs Are the Future
28mEmbracing Remote Development for Local IDEs
46mBuilding the IDE Golden Path
24mUnleashing Developer Productivity: Supercharging Zero Day Cloud-Native Developer...
25mWeb-based Tools and IDEs: Accomplishments and Opportunities
34mKick ass code editing and end to end JavaScript debugging
27mHow browser IDEs are enabling the transition of development to the cloud- 46mSponsored Session: Building the IDE Golden Path