Geany vs Eclipse Che

Geany is very lightweight thanks to the smaller offering of features.

Geany has a built-in plugin manager which can be used to install plugins and add new powerful features to the editor.

In Geany you technically search once for a whole search query, unlike Gedit, where once you start typing, the file is searched for in accordance with each substring of what you're typing, all the while leading to terribly annoying lag.

Geany is a cross platform editor, very similar to Notepad++ in Windows.

Press F5 and code will run without the need to switch between windows.

This software respects your freedom.

Hence it is capable of showing the methods and inner classes of, e.g., a Java source file.

It is a real app and not another frankenstein web/electron app. This means it runs great and doesn't extraordinary amounts of RAM.

For example, there is an easy way to change the font and theme in the View menu. No need to search through several syntax styles like in Notepad++ just to be able to change the used font.

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.