Sequel Pro vs hyper
When comparing Sequel Pro vs hyper, the Slant community recommends Sequel Pro for most people. In the question“What are the best power user tools for macOS?” Sequel Pro is ranked 22nd while hyper is ranked 72nd. The most important reason people chose Sequel Pro is:
Clean, easy to use, highly polished interface.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Great UI
Clean, easy to use, highly polished interface.
Pro Native OS X from the start
Unlike other solutions, Sequel Pro was built specifically for OS X and for MySQL from the beginning and as such the design takes better advantage of OS X features and is optimized for MySQL.
Pro Free and open source
Licensed under MIT.
Pro Multiple connection methods
Sequel Pro can choose between standard and SSH connection methods.
Pro Multiple import/export options
Sequel Pro can export to SQL, CSV and XML files and import SQL and CSV files.
Pro Command line access
Sequel Pro can also access and manage everything from the command line.
Pro Excellent user management
Has easy user privilege management.
Pro Highly flexible filters
Sequel Pro has highly flexible and customizable filters.
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 Crashes constantly
Crashes when working with mysql 8.0.12 for macos 10.13. Unable to do anything.
Con Not maintained
The app crashes when you close a tab.
Con No MySQL 8 support
Con Not adapted for MacOS Catalina
Con No multiple query tabs
Sequel Pro does not support multiple query tabs in its editor. This is incredibly frustrating for a power user.
Con Text in the query lost on connection failure & crashes
Con OS X only, no Linux or Windows versions
Power users have to manage in many different environments. A consistent admin interface is hugely beneficial.
Con Query editing capabilities much poorer than MySql Workbench, Querious, and others
Con No visual query editor
Con Unable to import from binary SQL files
I frequently import binary multipolygon data from another source, and it won’t open.
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.