Hi Alex:
Thanks for your thoughts.
Over the past many months, we have been working on strategies for better modularization. As a first step, we needed to remove a lot of libraries that were being deployed into each agent that were unnecessary. We have recently completed most of that work, and this subsequently makes the packages for what goes onto the agent and master much smaller. Additionally, the next step we are working towards is enabling each workspace to host a separate configuration of plugins / extensions. So it will be possible for each workspace in a single Che server to have a different set of extensions / plugins, whether they are server-side or client-side. This poses a variety of challenges around browser caching, especially when you have a single user bouncing between two workspaces with different configurations. We also have a good vision of decoupling a lot of our agent capabilities into micro services that can be deployed and run independently within a workspace runtime, further reducing the elements that need to be packaged into a single workspace agent.
What company do you work for and what projects are you thinking about? The next Eclipse Che planning meeting is next Tuesday, May 31st at 7am pacific time. There is a public google hangout that anyone can join. Perhaps your team can join the call, learn a bit more about the current roadmap, and hear about various directions that can be taken?
Tyler