Next generation Eclipse enters Cloud _java

Take us together to understand the "next generation eclipse into the cloud"

First, installation method
Note: Che is currently a pre-alpha version, please compile from source code to experience the concept of workspace/environment.

Che needs docker and can view information about Windows or MacOS installation Docker as needed.

Installation method:

 git clone

 git checkout 4.0 
 CD ASSEMBLY-SDK
 mvn clean install

 CD ...
 /che Run
 http://localhost:8080

Second, nuanced design

Auto-complement function

Light Theme

Che online editor

Using GitHub

Third, Workspace server
With restful APIs, you can customize project types, customize commands, and fit any device.

✔restful APIs
✔ Support Browser, mobile end, CLI, desktop client
✔ Fast, scalable
✔ Service-side extensions
✔ The service side provides an interface that can be overwritten
✔ Support SDK
Che's APIs run through the entire development cycle, providing one-stop service from editing to debug to automatic execution and deployment, making development more secure and faster.

Four, Plug-ins
Che has a rich plugin that you also open to write your own plugin.

V. Comments
Some netizens mentioned:

Considering that the current compiler occupies such a high resource (for example, C + + compiler), this will be separated from the front and rear, lightweight front-end only responsible for editing code, back-end Unified processing interpretation, compilation and so on. This can even save memory.

But what I like is that whenever people want to use HTML when they think of doing client/server side, HTML is no good for me. The cost of setup is negligible, I do this line, OK? I know how to install the program, not to spend this time.

However, there are only two ways to do the front end with Js/dom:

1, the front-end code into JS: Very stupid simulation js, need to worry about interactive issues.
2, use JS to write: To endure the bad grammar
The IDE is the most complex GUI, why do you need this language to add complexity? If you write with something like JavaFX, I believe that development will be much simpler and quicker.
A netizen expresses approval:

Eclipse is slow enough before the js/dom. The ancient Emacs was written in Lisp, but it ran very fast. Now a lot of scripting language editors like atom and light table are slow
Codenvy Official Tylerjewell response:

The point is not to use HTML. Our goal is to provide an IDE that can be used anytime, anywhere. I've had a bad history of development tools: After seven years of writing code, I want to write a little bit of code, and I can't compile a simpler program.

I came up with the idea that people could get into a project anywhere, anytime, without installing any software. With just a few clicks, everything is configured: the workspace, the project in the workspace, the environment that drives the workspace.

Now, if you use the desktop side, you can use a workspace that combines with the IDE. But if you are a product manager and want to test the code, you may not want to configure a complex environment. Then the browser experience comes in handy.

So far, we have not fully hosted the IDE in the cloud, so we started this project, for people who do not want to spend energy in the configuration environment, is a rare product.

We chose GWT to develop the GUI because it has good browser compatibility and good performance. Although it is rough, but we do a lot of optimization. At the same time we also do the dynamic loading and plug-in support, and so on. We also have partners to our Pure JS client technical support.

We will embed all programming languages in the machine running the development environment, which can be configured to use localhost or docker. By then, the difference between the browser and the workspace will not be too great to expect to bring a good experience. File operations are done locally, so the speed reaches 50k lines (Java files) and can rival Eclipse and NetBeans.

This is the first of the next generation eclipse, I hope you will enjoy it.