When comparing hyper vs mRemoteNG, the Slant community recommends mRemoteNG for most people. In the question“What are the best SSH clients for Windows?” mRemoteNG is ranked 19th while hyper is ranked 24th. The most important reason people chose mRemoteNG is:
Open source.
Ranked in these QuestionsQuestion Ranking
Pros
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
Pro It's free
Open source.
Pro Import/Export feature
Allows to share connections.
Pro Can open multiple sessions in different tabs
Pro Connection manager
Lets you organize your connections into folders with icons as well and allows nested folders as well.
Pro Supports multiple protocols
RDP (Remote Desktop/Terminal Server)
VNC (Virtual Network Computing)
ICA (Citrix Independent Computing Architecture)
SSH (Secure Shell)
Telnet (TELecommunication NETwork)
HTTP/HTTPS (Hypertext Transfer Protocol)
rlogin
Raw Socket Connections
Pro Inheritance from folder properties
Inheritance makes it possible to store properties on folder basis and let the underlying connections inherit this info.
Cons
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
Con Private keys needs to be managed on PuTTY
Since mRemoteNG is integrated with PuTTY (included in the installation), all private key needs to be configured on PuTTY itself and then the PuTTY session needs to be selected on mRemoteNG.
