Eclipse Che vs Yi

Built-in terminal with root access so you can make changes to your running machines. Being able to SSH into the workspace so you can use a desktop IDE is handy.

You can package up custom commands with your workspace and then use them (or share them) with everyone else.

You can choose from pre-configured environments for Java, Javascript, C++, PHP, C#, etc., or you can define your own by dropping in a Dockerfile - makes it easy for simple and complex projects.

Projects can be easily imported from any Git or Svn repository hosting service.

The workspace in Che includes project sources, IDE and the runtime. So if you hand your Che workspace definition to another user and they execute it they will get everything they need to build, run and debug the project.

Also the runtime is in a Docker container so it will work even if the second user is on a different OS than the original user who shared their workspace with them.

Che does a nice job to automatically map the service:port running in the Docker container (e.g. tomcat on 8080) to the Docker port it actually uses (something in the ephemeral range). You never need to figure that out - it's just made available when you run your server.

Yi has default configurations for Vim, Emacs, as well as CUA. It also makes several improvements that includes Sublime-like (multiple) cursors.

Vim can be rather slow due the age of its code base. In particular, running large macros in Vim can be rather painful. Since Yi is being built from scratch it has been engineered for performance and with the benefit of hindsight.

As far as extensibility goes, Yi easily outstrips any other open-source text editor. Motions can be built from parser combinators, making them simultaneously flexible and modular - an open source hacker's dream.

Packages work together because they compile together.