When comparing Enso Portable vs Docker, the Slant community recommends Docker for most people. In the question“What are the best power user tools for Windows?” Docker is ranked 43rd while Enso Portable is ranked 50th. The most important reason people chose Docker is:
Docker creates a single object, containing an application with its dependencies, that can be moved between any docker-enabled machines, guaranteeing the same environment for application execution.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Extensible in Python
GChristensen recently upgraded Enso to Python 3.7, a great improvement over the original v2.5. You can write custom Enso commands in Python through its new web interface (or your favorite editor once you know where to put the files.) There's even an install command to pip install any Python package you need from PyPI. The sky's the limit.
Pro Optional quasimode
Letting go of CapsLock just feels faster than hitting enter (sometimes too fast: be sure to disable the reboot command before turning this on!) Even with quasimode enabled, you can make it modal for that command by tapping Alt.
Pro Easily teach the app to open specific apps and sites
There is a learning function to the app that allows the user to teach the app to open specific items by typing "learn as open" and then clicking on the item one wants it to learn to open.
Pro Can go to existing open windows
By using the "go" command users can switch to their already open windows making this a bit of a window navigator as well as a launcher.
Pro Allows for portable application deployment
Docker creates a single object, containing an application with its dependencies, that can be moved between any docker-enabled machines, guaranteeing the same environment for application execution.
Pro Git-like capabilities
Docker tracks changes in systems. It allows for commits and rollbacks and for quick deployment due to having to deploy only the updated code.
Pro Allows re-using components
Docker essentially allows creating boilerplate systems (a LAMP stack, for example) that can be used as a starting point on multiple projects. And you can find multiple such containers already created by people in their public registry.
Pro Automatic build
Allows automatically assembling a container from its source code.
Pro Provides easy sharing and installation of containers through a public registry
Docker allows easily pushing and pulling containers to and from their public index.docker.io registry. Additionally, dotCloud maintains a list of official repositories of the more popular containers.
Pro Application-centric
Pro Works in virtualized environments
You can set up Docker within an already virtualized environment such as a virtual machine. This allows you to run Docker on Mac and Windows, among other use-cases.
Pro Low overhead
Pro Supports a wide range of isolation tools
Docker can be used with OpenVZ, systemd-nspawn, libvirt-lxc, libvirt-sandbox, qemu/kvm, BSD Jails, Solaris Zones, and chroot.
Pro Tool ecosystem
Cons
Con Comes with a reboot command
And a shutdown command too. Installing these is optional, and I recommend that you don't, especially if you use the quasimode. Unless you like losing your work.
Con No message log
According to Raskin's philosophy which inspired Enso, a pop up "dialog" is a bad design. The OK button is a useless input that interrupts your flow. Enso's pop up messages, therefore, are transparent and quickly fade away on their own (like Android Toast messages). Unfortunately, this also means you can easily miss them if you're not paying attention. Raskin's solution was to keep a message log you can refer back to, but Humanized never got around to implementing that for Enso.
Con Usage tends to be slowed by the caps lock
Function of the app relies on the caps lock key being pressed to enter commands, which can slow some people down by having to hold that key down when they are typing commands.