When comparing KiTTY vs Alacritty, the Slant community recommends KiTTY for most people. In the question“What are the best terminal emulators for UNIX-like systems?” KiTTY is ranked 2nd while Alacritty is ranked 7th. 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
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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
- Transparency
- Quick start of a duplicate session
- SSH Handler: Internet Explorer integration
- pscp.exe and WinSCP integration
- New command-line options
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 Source Code Available
Source code is available so you could modify or review changes.
Pro Can store login credentials
Ability to store passwords/passphrases locally.
Pro Clickable URLs
URLs are parsed and can be clicked.
Pro Auto login script
Automatic processing of commands after conncetion was made.
Pro True Color support
Supports True Color, so software like Vim can display a really nice pallet.
Pro Portable version available
Pro Background image
Ability to overlay the terminal background with an image.
Pro Unicode
Uses Unicode for the best character compatibility.
Pro Blazing fast rendering with GPU-accelerated
Written in Rust with a philosophy focusing on speed and simplicity, Alacritty is one of the fastest terminal emulators out there.
Pro Looks good
Alacritty looks very slick on Linux, especially with GNOME or i3.
Pro Simple configuration
The configuration file is very well made and easy to use. You can fine tune your preferences to perfection in a matter of minutes.
Pro Comprehensive font options
Alacritty can be configured to adjust line spacing (height), letter spacing (width), and individual character horizontal/vertical positions.
Pro Has support for image previews in w3m and ranger
Pro Has text ref-low when window is resized
Pro Fast and simple but with true color support
It's simple and fast like xterm or urxvt but with truecolor support which is a big plus if you use a terminal based code editor. Basically Alacritty has all the features you need and nothing you don't (if you're using tmux for multiplexing).
Cons
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 No mouse support in alternative screens
Like vim, less, etc.
Con Cannot into ligatures
Alacritty does not support ligatures in Fira Code, Iosevka etc.
Con Unreliable Font Rendering
Like a box of chocolate you never know what you're going to get.
Con Sacrifices basic features for raw performance
The Suzuki GSXR of terminals. Or your ditzy, blonde high school cheerleader; fast and pretty but not a lot going on under the hood.
Eschews a negative developmental philosophy towards including said functionality, with the official reason cited in project documentation as "Not within the realm of a terminal emulator" and ostensibly, "best left up to other tools such as terminal multiplexers" [such as screen or tmux]. Which is unfortunate when you factor in speed against terminal with the functionality built in vs their reliance on 3rd party tools:
tmux on alacritty: 'find /usr' time: 3.234s, cpu: 72%
tmux on konsole: find /usr' time: 1.777s, cpu: 96%
See issue here.