When comparing Divvy vs hyper, the Slant community recommends Divvy for most people. In the question“What are the best power user tools for macOS?” Divvy is ranked 17th while hyper is ranked 72nd. The most important reason people chose Divvy is:
Although it's not in the same level as something like bug.n, Divvy does support the use of keyboard shortcuts to move windows about. You can even create custom shortcuts.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Has keyboard shortcuts
Although it's not in the same level as something like bug.n, Divvy does support the use of keyboard shortcuts to move windows about. You can even create custom shortcuts.
Pro Requires virtually no configuration & is very easy to use
Divvy uses a drop and drag style UI that's simple to use and doesn't require any setup or configuration to get started.
Pro Reasonably configurable
You can change the grid dimensions and a very other visual settings to suit your needs.
Pro Super-fast access by defining your own hot key (mine Win+S)
Pro Cross-platform due to electron browser-based foundation
Although not Windows-friendly. But nobody uses Windows terminal anyway.
Pro Built on electron, supports split panels and plugins
Cons
Con Quite inconvenient to assign windows
You always have to use the mouse instead of having proper keyboard shortcuts.
Con No longer updated
While this may work for current machines, the last beta version (to be found on the site) is from January 2016.
Developer's twitter account has stopped being active as well, on November '16.
Con Windows 10 buggy
Not all keyboard shortcuts work. Support is non existent.
Con Installer requires admin rights, installs itself to AppData of the used account
Something to consider if would be used in a restricted environment.
Con Not free
Costs $14.
Con Made with Electron
It uses a considerable amount of resources, compared to other offerings.
Con Not as cross platform as advertised
Most features only work on Mac OS.
Con Incorrect rendering
Terminal window has visual artifacts.
Con No configuration UI; all options must be set via JSON
Con Still maturing as of December 2016
Folks noticed some issues in the 1.0 release cited here.