[dead]
The DuckDB Local UI
121–130 of 197 posts
Re: The DuckDB Local UI
#122Weirdly, as cool as this looks, it's a bit concerning to me. It feels like this is marking a milestone in the history of a great open source project where they are doing one or many of the following: 1) Biting off more than they can chew, 2) Putting significant effort into something that's outside of their core value proposition, 3) Leaning more in the direction of supporting things with a for profit company that gra…
duckdb labs didn't make the UI, motherduck did. The extension just launches the web UI.
you might have a point on #3, but they need to pay the bills somehow.
Re: The DuckDB Local UI
#123Anecdote. Last year I had to work with a heavy analytics process. The whole thing was 4 or 5 large steps and was written with PySpark. It was really slow and memory on my system run quite low (on a 8Gb system with a generous swap), sometimes even stopping the whole processing of the pipeline. For one heavy step we tried out DuckDB and I was blown away how performant against PySpark was. It was not only fast as hell b…
simple example along these lines running on AWS (specifically paired with Iceberg): https://www.definite.app/blog/cloud-iceberg-duckdb-aws
Re: The DuckDB Local UI
#124Duckdb and polars have changed my Python development completely. Great packages that can work together, excited to see this.
wondering why just polars is not enough?
Re: The DuckDB Local UI
#125how come DuckDB manages to keep delivering such great new features?
Re: The DuckDB Local UI
#126I see many folks trying to build UI for multiple databases, when excellent open source solutions like DBeaver exist. Is there a reason to use this UI compared to DBeaver, through which I can interact almost all major databases?
Re: The DuckDB Local UI
#127Other commented on the frontend not being open source at the moment (which I hope they will eventually come around and OS it). But I just wanted to say how great this feels. In particular, being able to launch from within the CLI is a godsend because sometimes you start in the CLI and then realise you are better served with a GUI due to data complexity, etc.
Re: The DuckDB Local UI
#128Earlier quoted context omitted.
The actual UI is not open source. (Someone could write an actually open source UI extension for duckdb, but that would require a lot of investment that so far only motherduck has been able to provide.)
I've looked at quite a few options, and this one (the product of a single person) is a great base, and MIT licensed: https://github.com/caioricciuti/duck-ui If you want to support a real OS UI take a look.
I’ll never understand how any UI projects don’t include an actual screenshot of their project as the first thing on their landing page. It seems so obvious.
Re: The DuckDB Local UI
#129Weirdly, as cool as this looks, it's a bit concerning to me. It feels like this is marking a milestone in the history of a great open source project where they are doing one or many of the following: 1) Biting off more than they can chew, 2) Putting significant effort into something that's outside of their core value proposition, 3) Leaning more in the direction of supporting things with a for profit company that gra…
duckdb labs didn't make the UI, motherduck did. The extension just launches the web UI. you might have a point on #3, but they need to pay the bills somehow.
The fact that this is what they need to do to pay the bills doesn't decrease my concern, it increases it.
Re: The DuckDB Local UI
#130Earlier quoted context omitted.
> Spark is for when you have a hundreds of machines worth of processing to do Absolutely agree. However, most uses of Spark I've seen in my career are people thinking they have hundreds of machines worth of processing to do.
And even when you jave quite a lot of machines worth of processing some single threaded streaming of data on a single machine can still beat out any distributed framework as the the overhead of distribution is large.
A favorite paper, “Scalability! But at what COST?”. Authors show a single machine implementation (even single threaded) can wipe the floor with the maximum parallel capable implementation.