When comparing KiTTY vs hyper, the Slant community recommends KiTTY for most people. In the question“What are the best Linux terminal emulators?” KiTTY is ranked 4th while hyper is ranked 26th. The most important reason people chose KiTTY is:
- Sessions filter - Shortcuts for pre-defined command - The session launcher - Automatic logon script - URL hyperlinks - Running a locally saved script on a remote session - Send to tray - Transparency - Quick start of a duplicate session - SSH Handler: Internet Explorer integration - pscp.exe and WinSCP integration - New command-line options
Ranked in these QuestionsQuestion Ranking
Pro Includes additional features over PuTTy
- Sessions filter
- Shortcuts for pre-defined command
- The session launcher
- Automatic logon script
- URL hyperlinks
- Running a locally saved script on a remote session
- Send to tray
- Quick start of a duplicate session
- SSH Handler: Internet Explorer integration
- pscp.exe and WinSCP integration
- New command-line options
Pro Can store login credentials
Ability to store passwords/passphrases locally.
Pro Source Code Available
Source code is available so you could modify or review changes.
Pro Startup sessions
Support start-up sessions which allow you to specify the window/tab layout, working directories, and programs to run on startup.
Pro True Color support
Supports True Color, so software like Vim can display a really nice pallet.
Pro Background image
Ability to overlay the terminal background with an image.
Pro Auto login script
Automatic processing of commands after conncetion was made.
Uses Unicode for the best character compatibility.
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
Con No centralized configuration
Each session holds its own configuration of all features. This means that if one wants to change a configuration common to all sessions (say, the terminal font), it has to be changed in each stored session separately.
A better solution would be to have a default configuration and store only the changed elements for each session (both configurations would be merged, with e priority on the specific one).
Con No tabbed sessions.
No built in support for tabbed sessions. Requires an add on.
Con Made with Electron
It uses a considerable amount of resources, compared to other offerings.
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.