I love that this looks very much like Query Analyzer, the lightweight querying tool that came with SQL Server 2000. Back then, server management, querying and profiling were handled by separate utilities that did one thing well.
They were all replaced with SSMS, which was a slow abomination.
Query Analyzer is my favourite SQL editing environment to this day. It was incredibly snappy, could render thousands of rows without skipping a beat and had a nice explain visualisation built in. If there was a modern rewrite that supported PostgreSQL, I'd buy it in an instant.
There are screenshots in these articles if anyone's interested:
I don’t think it has the explain visualization, but otherwise these screenshots look a lot like DBeaver to me. Perhaps worth a try if you haven’t stumbled upon it yet.
dBeaver is written in Java, but it feels very lightweight. I'm running it on a Linux desktop I've been using since 2014. It's also cross platform so I run it at work on a Windows laptop.
Written correctly, Java can be both very fast and light. Eclipse IDE, written with Java consumes less resources than a comparable Atom/VSCode instance, with more features enabled.
Electron apps are not exactly lightweight either; it is about first time that someone uses them in an argument.
Query Analyzer was written with win32-api. No electron, no java, no c#, nothing (thought it might used MFC, not sure about that). It was snappier on Pentium 3 than Dbeaver is on M1 or Threadripper. Existence of slow molasses like Electron won't change that.
I didn't use DBEaver, but written some Java and using Eclipse for 20 years.
Java's UI libraries are extremely prone to wrong initialization. If you skew from the reference guide's implementation, Java's libraries try to mend the problems themselves, but this adds observable latency to the UI.
Of course, Java is never as fast as natively compiled language, but asymptotically approach to that speed and come pretty close. The funny thing is, some of the today's native applications are both heavier and less responsive w.r.t. their Java counterparts. This is because we tend to add loads of dependencies which aims to simplify development in said language, but that price is always paid at the end. Either once by the developer, or repeatedly by the user.
It's not feature complete, but Data Studio felt like a breath of fresh air compared to SSMS being all the slowness of Visual Studio coupled with about 1500 places where configuration might be.
(Of course, what do I know. I use DataGrip for my databasing these days. It's fine.)
They were all replaced with SSMS, which was a slow abomination.
Query Analyzer is my favourite SQL editing environment to this day. It was incredibly snappy, could render thousands of rows without skipping a beat and had a nice explain visualisation built in. If there was a modern rewrite that supported PostgreSQL, I'd buy it in an instant.
There are screenshots in these articles if anyone's interested:
http://etutorials.org/SQL/microsoft+sql+server+2000/Part+II+...
https://www.sqlservercentral.com/articles/using-query-analyz...