When comparing cool-retro-term vs hyper, the Slant community recommends cool-retro-term for most people. In the question“What are the best terminal emulators for UNIX-like systems?” cool-retro-term is ranked 18th while hyper is ranked 24th. The most important reason people chose cool-retro-term is:
Cool-retro-term mimics the look of old cathode screens. This is just aesthetic, but great for people who want a more retro feel.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Mimics the look and feel of the old cathode tube screens
Cool-retro-term mimics the look of old cathode screens. This is just aesthetic, but great for people who want a more retro feel.
Pro Good rendering
If you disable every special effect and the framing, the rendering is actually quite comfortable and readable making a good terminal option if you have CPU cycles to spare.
Pro Good fun
For simple tasks this is wonderful - anyone seeing it will love it, takes me back to using the Commodore Pet in college in the early 80's.
Pro Available in multiple repositories
This terminal is available for download from repositories in all the most popular distros, making it easily available.
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 Not very practical by today's standards
While it certainly has an aesthetic feel, cool-retro-term is nothing more than a cool trick if you want to play around. It's not very useful in this day and age.
Con Extremely heavy and impactful on resources
A massive amount of resources are used as graphical processing in cool-retro-term. They are ridiculously heavy for the terminal's intended use.
Con Large dependency on kde
It looks like many of the effects present here are provided by more or less stock kde effect libraries. For Gnome-based systems, installing this will pull in a large handful of kde libs.
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.