When comparing ROXTerm vs hyper, the Slant community recommends ROXTerm for most people. In the question“What are the best terminal emulators for UNIX-like systems?” ROXTerm is ranked 21st while hyper is ranked 24th. The most important reason people chose ROXTerm is:
ROXTerm supports dragging and dropping items into the Terminal window.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Drag and drop
ROXTerm supports dragging and dropping items into the Terminal window.
Pro Advanced D-Bus usage
In ROXTerm, users can use D-Bus to configure terminals from other applications, allowing for communication between multiple computer programs.
Pro Includes a configuration manager
ROXTerm includes a configuration manager which can easily be run by selecting Configure...
in the terminal's menu, or by simply running roxterm-config
. You can then easily swap configuration files with other users, manage profiles, and customize things like color schemes or keyboard shortcuts.

Pro Supports GTK3
ROXTerm uses the latest GTK widget set which is great a multi-platform toolkit for creating graphical user interfaces.
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 Uncertain future
The original developer, Tony Houghton, declared the death of Roxterm on 2016-05 at https://sourceforge.net/p/roxterm/discussion/422638/thread/60da6975/?limit=25#3fc9.
In 2018, work began to resume on Github rather than Sourceforge (https://github.com/realh/roxterm/issues/1) but the future maintenance is uncertain.
Con Not for regular users
ROXTerm is made for power users who spend most of their time on the terminal. For a regular user using ROXTerm it would be an overkill.
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.
Con Difficult to find information about it, because of the confusion with hyperterminal
