Switched to DBeaver from DataGrip

DBeaver is faster:

• My commands go through immediately
• It has a better FPS

The interface of DBeaver is simpler. Less clutter, more information.

It has better support for JSON; In DataGrip's Value Editor, for some reason, stringified JSON inside of a JSONB column turns into plain JSON instead of staying stringified, which means I can't copy paste values from or to the Value Editor without first manually converting them back into stringified JSON or vice versa.

Also I cannot make the Value Editor STAY in DataGrip. Every time I re-start DataGrip, or I open a new tab, I have to open Value Editor again.

It has a more intuitive handling of saving "scripts" for a given connection.

DBeaver's Community Edition is everything I need for SQL, and it's gratis.

For MongoDB, which I also had in DataGrip, I just use MongoDB Compass. It's a much better designed interface for JSON objects than DataGrip is, even though I like DataGrip more for its script-writing capabilities for Mongo (I can write scripts, in MongoDB Compass I'm stuck with a rather clunky interface for that). If I ever miss that too much, from DataGrip, I can always start paying for DBeaver.

Let this be a reminder to the market: performance matters. Pretending otherwise is foolish.

I have one gripe with it, which is that I can't do Ctrl-e to go to the end of the line, in macOS.