Brackets vs Eclipse Che

Brackets will automatically refresh the browser and load the latest saved version of a file open in the browser. This works with php as well. Editing a css will even highlight the tag that's currently being worked on. However, it only works with Chrome.

Brackets is easy on memory usage and it starts up quickly.

Brackets is entirely free and open source.

The functionality of Brackets can be extended via a simple-to-use extension manager. The extension manager also has a considerable number of extensions and themes.

A feature called "Quick Edit" allows the user to select a tag in (a html file, for example) and edit the associated style without switching over to the css document. It also supports SASS and LESS pre-processors.

Brackets is being actively maintained and developed.

Hovering over colors hex codes or image paths will pop up previews of corresponding colors and images.

Brackets supports drag and drop of text, as well as multi / rectangular selection.

The editor is built using html, css, and javascript, making it extendable by any front-end developer.

You can have your cursor independently on multiple lines and so creating templates and/or editing multiple things at once is really fast and easy.

Vim-style editing is already built in the text editor.

A default extension allows for the extraction of PSD resources, such as images and styles. There's good integration for placing extracted resources into source.

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.