[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[che-dev] Maybe it's time to admit
|
...that our plugin model (contanier per plugin) is wrong:
* we're investing a lot of effort into our container-per-plugin model,
yet we can't really make it work for many vs code extensions, leading to
weird errors and testing effort at each update
* we need to run our own plugin registry with our own meta.yml, etc.,
which is becoming a bottleneck
* we need a "dev-machine" image anyway (for example, with maven, npm,
typescript or whatever the stack needs)
* the focus seems to be on out-of-the-box experience, which could easily
include making a specific "IDE" image per stack.
* there is an effort to make the different containers invisible to the user
* all other contenders in the market have a "single container for the
IDE" model
* the model only works for Theia and we seem to be starting to support
other editors
I was excited about our plugin model in the beginning, as well, but if
we're not using it as a competitive advantage and we don't have the
resources to make it work well, I'm starting to doubt it's worth the
complication it adds.
discuss....
/Thomas
