When comparing Eclipse Che vs Google VM Instance, the Slant community recommends Eclipse Che for most people. In the question“What are the best cloud IDEs?” Eclipse Che is ranked 6th while Google VM Instance is ranked 15th. The most important reason people chose Eclipse Che is:
Ranked in these QuestionsQuestion Ranking
Pro Docker runtimes
Pro SSH + terminal
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.
Pro GIT and SVN VCS support
Projects can be easily imported from any Git or Svn repository hosting service.
Pro Reproducible environment
Pro Custom commands
You can package up custom commands with your workspace and then use them (or share them) with everyone else.
Pro Portable workspaces
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.
Pro Merge tool for VCS
Pro Total environment control
Pro Can run any sort of web-based editor software
For example, one can run Jupyter Notebook on the VM.
Pro Real vi or Emacs editor
Pro Real Linux console
Con Slow runtime
Online IDE is much slower than desktop one.
Con This is not a "cloud IDE," this is a remotely accessible virtual machine.
This topic is about the best cloud IDEs and having a Google VM Instance on the list is a bit of a stretch. That's not to say that the service isn't valuable or great, but it is a completely separate purpose. Granted, you can certainly install the necessary tools on your virtual machine to make it an IDE that is remotely accessible, but that's not exactly the ideal situation and not what someone looking for a cloud IDE is likely looking to do.
Con Can be expensive
If one selects a powerful type of instance or if one does not take care and remember to shut off the instance when it is not being used.
Con Less ideal if you have a slow internet connection
Though this applies to any Cloud IDE, as well.
Con Less ideal if you are mouse dependent
Assuming you are using Vi or Emacs, and not Jupyter or some other web-based editor that is running on the remote VM instance.