Whats the advantage of this over something like dbx (https://github.com/t8y2/dbx)?

DBX is great but it uses tauri, it is better than using jvm and electron but still doesn't provide the performance gains GPUI does or any other native framework would do.

▲

mbreese 5 hours ago | parent | next [-]

Performance is a hard sell when most of the time is going to be spend waiting on the DB for queries, isn't it? (compared to dbx - anything in Java is going to naturally be larger for this).

Or are you thinking of performance in terms of UX when browsing the result-sets?

But, congrats on the project. It looks great. I can't wait to try it.

	▲	shayan_abbas 4 hours ago \| parent [-]
		Yes, the slow queries stay but there are some differences: Same result set where other clients can crash, this scrolls smoothly so you can naturally load a bigger result set in the app than other clients would allow you to, It paints the UI considerably faster than DBeaver on my benchmarks, thats after the query has run. Memory footprint for the same result is considerably lower. Basically, your db client can slow you down even after you have waited for queries so this will fix that.

▲

dubcanada 5 hours ago | parent | prev [-]

So your main sell on DBDelve is performance?

	▲	shayan_abbas 5 hours ago \| parent [-]
		Yes, and UX. Doing the fundamental things but doing them really well. I like zed's approach where they were slow to add features and weren't/aren't at feature parity with VSCode but the point was to get out of the way for most of your workflows. I'm basically going with the same idea in mind.