From: Tyler Jewell <tyler@xxxxxxxxxxx>
For your points:
1. I have cc'd the engineers that have spent the most time either
architecting the plug-in framework, and / or using it to build our plug-ins
especially the Java / Maven ones.
2. As a general rule, the objective is to be able to plug existing
libraries for various languages to run natively within the workspace, and
then to create Che plug-in wrappers around those libraries, turning them
into RESTful services. This is what was done for Java, and some _javascript_.
I believe that our abstractions are clean here, but I imagine that the
cleanliness of the abstractions themselves get stronger as more languages
are added in. I am just the project lead, not the architect - so those
CC'd can provide better descriptions.
Could you share a little about which languages you'd like to add support
for?
Tyler Jewell
Hi Tyler,
Thanks for your answers.
I am currently the developer for erlide, the Eclipse support for Erlang. The evolution of the architecture has been from a fully Java implementation towards using an Erlang runtime as a backend for the IDE services. My biggest architectural problem has been coming up with a remote API, hopefully a generic one. I still don't have a good one and when I read about Che, I realized that its APIs might be just what I needed.
Also, many Erlang users are using it for developing web applications and they would benefit from being able to use Che instead of the regular Eclipse, as it's better suited for web development, so I am also looking at providing Erlang support for Che.
best regards,
Vlad
