Build it and You'll Learn: A Discussion About Lessons Learned Building Cloud Tools
summary
Panelists describe concrete builds and outcomes: a browser-hosted Eclipse Jefferson mainframe extension that runs one codebase across Eclipse Che and GitHub Workspaces to edit z/OS apps, a code-server that delivers 99% parity with Microsoft marketplace extensions by crawling GitHub, and Gitpod/Coder workspaces that push ephemeral cloud compute but must fight abuse like crypto miners. Challenges include browser testing, Docker home directory quirks, keeping up with VS Code API churn, and devcontainer/runtime standardization.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:10Welcome
- 1:50Introductions
- 2:35Questions
- 4:05Inspiration
- 5:25VSX Registry
- 6:35Inspiration for Building
- 8:05Lessons Learned
- 10:48Challenges
- 13:25Growing pains
- 14:30Making VSX registry viable
- 16:40Removing friction
- 17:45Driving adoption
- 19:10Turning point
- 20:23Adoption
- 21:56Developer Ecosystem
- 23:34Simplified IDEs
- 24:30VS Code Extension API Compatibility
- 25:14VS Code VSX Registry
- 29:15Standardizing APIs
- 30:44Dev Container Format
- 32:28The Future of IDEs
- 33:10Wrap Up
related talks
24mEclipse Che & the future of Cloud Development Tool
45mContaining Your Development – Why Cloud IDEs Are the Future
06mLeveraging Eclipse Che for developers
47mPanel Discussion - Theia and the Cloud Development Ecosystem Where it fits now and what do
46mSponsored Session: Building the IDE Golden Path- 46mBuilding the IDE Golden Path
45mEclipse Che
36mIf, when and how? - Strategies towards web-based tooling