Recs.
Updated
SpecsUpdate
Pros
Pro Docker-based workspaces
Allows anyone to build and test your application from anywhere. Starts a Docker image and mounts your project into it, allowing your to control the runtime environment. Out of the box Che uses Docker as runtime provider but can use a remote SSH or many other. A custom Stack is basically you writing a Dockerfile.
Pro SSH terminal
Che injects an SSH daemon into workspace machines. Connect your existing IDE–Eclipse if you like–with an SSH sync point. Upload your key pair or have Che generate a new pair for each workspace. You can also access your workspace with Che's browser terminal, giving you root access to workspace machines.
Cons
Con Single-user, no authentication
Eclipse Che is single user without even any authentication (it's recommended to run it behind Nginx to add authentication). One can run an instead for each user or switch to Codenvy (which is a multi-tenant, multi-user, elastic implementation of Che). Currently it is unsafe to deploy it on a publicly accessible network, and Che behind Nginx isn't enough, because other ports don't use HTTP protocol and also require no authentication.
Con Currently no search and replace in multiple files
There is a search in multiple files, and search & replace in current file, but not something to perform a search & replace in multiple files. However using the terminal to perform such operations is possible (if you know how to do that).