The main idea is to stop maintaining
CDT Cloud Blueprint as a standalone product and instead integrate its CDT Cloud specific extensions and capabilities directly into the
Theia IDE.
From my perspective, there are a couple of clear advantages:
- Maintenance effort is reduced because we no longer need to maintain a separate product.
- Increased visibility of CDT Cloud extensions, as they would become part of the more widely used Theia IDE
- A more polished first experience for CDT Cloud users, since Theia IDE is more actively tested and maintained
- Opportunity for cross-dissemination, e.g., highlighting CDT Cloud topics in regular Theia communication channels
However, there are also some downsides:
- CDT Cloud extensions would live in a more generic IDE instead of a very CDT-focused product
- We would no longer provide a dedicated CDT-specific Theia template project
That said, since most CDT Cloud extensions are already VS Code extensions and thus easy to integrate into Theia IDE, adopters who want to build a dedicated embedded development tool can still do so by combining these extensions with Theia’s customization capabilities (as
documented in Theia) even without a dedicated Blueprint.
I'm curious to hear your thoughts on this. We’re planning to make a final decision during the next
CDT Cloud monthly on May 18th.
Thanks and best wishes,
