If, when and how? - Strategies towards web-based tooling
summary
Argues that web tooling (Eclipse Che, Theia, VS Code, Electron, Dirigible, Orion) is not a universal win and recommends a use-case-driven migration: evaluate installability, portability, performance, usability and cost, pick low-hanging fruits (tutorials, code review, quick contributions), build a POC, migrate iteratively and preserve investment by reusing language servers (LSP), CLI tools, Docker/workspace servers and embedding web widgets in the desktop to single-source functionality.
AI-written summary · about
chapters (20)
- 0:00Start
- 0:44Quick Disclaimer
- 3:34Typical Advantages of a Web-Based Solution
- 4:15Disadvantages
- 4:29Uncertainty about Frameworks
- 8:11Evaluate the Use Cases
- 9:45Install Ability
- 10:19Use Cases
- 11:47Quick Contributions
- 12:17Contrary Abuse Cases
- 16:18Alternative Mitigation
- 17:01Program Use Cases
- 19:20Key Decision Criteria
- 19:48Cost
- 20:45Decision Criteria
- 27:05Migrate Iterative
- 27:45Migrate Iteratively
- 32:13Single Sourcing
- 32:48Declarative Artifacts
- 34:35Key Takeaways
related talks
25mWeb-based Tools and IDEs: Accomplishments and Opportunities
36mBuild it and You'll Learn: A Discussion About Lessons Learned Building Cloud Tools
45mContaining Your Development – Why Cloud IDEs Are the Future
20mOrion: The web is my development environment
31mDX to another level
01h 29mTooling for the JavaScript Era
19mDevelop, Debug, Learn?
44mAdvancing the web without breaking it?