When comparing LilyTerm vs software.jessies.org terminator, the Slant community recommends LilyTerm for most people. In the question“What are the best terminal emulators for UNIX-like systems?” LilyTerm is ranked 19th while software.jessies.org terminator is ranked 36th. The most important reason people chose LilyTerm is:
You can also color and reorder tabs, as well as manipulate tabs through keybindings.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Support for tabbing
You can also color and reorder tabs, as well as manipulate tabs through keybindings.
Pro Transparency support improves usability
LilyTerm has true transparency support, making for better GUI usability.
Pro Change encoding on-the-fly
LilyTerm can change encoding on-the-fly. UTF-8 is the default encoding.
Pro Lightweight
LilyTerm is a terminal emulator that aims to be as lightweight as possible. It requires minimal system resources and has very few dependencies.
Pro Fullscreen support
LilyTerm has fullscreen support which improves visibility.

Pro UTF-8 support enables character encoding
Due to UTF-8, this terminator won't mangle your favorite accented characters, and it copes well with languages where there's a mix of normal and wide glyphs (such as Greek).

Pro Unlimited scrollback
Terminator won't throw away output when it scrolls off the top of the screen, nor when it reaches any arbitrary limit.

Pro Multiple tabs
This is just like tabbed browsing, only with terminals, and means that multiple pages or documents are contained in a single window.

Pro Horizontal scrolling
Most terminal emulators wrap text when it intrudes upon the right margin. Terminator doesn't; it instead provides a horizontal scrollbar when necessary.
Cons
Con Annoying behaviors
The default configuration may have some annoying behaviors (that can be removed by changing the default config). Such include asking for confirmation when reusing an existing window or when starting the terminal to launch a specific command.
Con Seems to have been abandoned
There are several issues posted since 2013 on the project repository that have not yet been solved.
