Live data from Hacker News

The DuckDB Local UI

duckdb.org

71–80 of 197 posts

Re: The DuckDB Local UI

#71
post #3

i’m one of the co-founders at MotherDuck. our team is building the UI in collaboration with the team at DuckDB Labs. this is a first release. we know there are going to be tons of feature requests (including @antman’s request for simple charts). feel free to chime in on this thread and we’ll keep an eye on it! meanwhile, hope you enjoy this release! we had lots of fun building it.

How do you compete with Supabase ? Do you have a built in authentication system? Anything like edge functions. I've been trying to build a small card game with Supabase and I'm sorta stuck...

Supabase IMO sits in the middle of the curve between Firebase and PocketBase, not really the same use case as DuckDB & MotherDuck.

Re: The DuckDB Local UI

#72
Just came here to say, the demo video was awesome!

Refreshing to neither see a loom recording or a high budget video set in a Japandi architecture style office designed to go viral.

Re: The DuckDB Local UI

#73
post #51

Earlier quoted context omitted.

Reminiscent of what Deno are doing with their Deno K/V feature, which works in the open source project using SQLite but gets a big upgrade if you use it with Deno Deploy: https://til.simonwillison.net/deno/deno-kv I'm OK with this. Commercial open source projects need a business model. I get why this can be controversial, but the ecosystem needs to find ways to fund future development and I'm willing to compromise on…

https://github.com/denoland/denokv You can self host Deno KV since over a year.

That doesn't change what they're saying. The self-hosted backend you're linking is a network-accessible version of the local SQLite backend. The hosted backend is transparently globally replicated and built on FoundationDB, with a very different (better) scaling story.

Re: The DuckDB Local UI

#75

The UI looks nice and is by itself a welcome addition. I am somewhat at odds with it being a default extension build into DuckDB release. This still is a feature/product coming from another company than the makers of DuckDB [1], though they did announce a partnership with makers of this UI [2]. Whilst DuckDB has so far thrived without VC money, MotherDuck has (at least) 100M in VC [3]. I guess I'm wondering where the…

One of the DuckDB maintainers here. To clarify - the UI is not built into the DuckDB release. It is an extension that is downloaded and installed like any other extension. This extension happens to be developed by MotherDuck. We collaborated with them to streamline the experience - but fundamentally the extension is not distributed as part of DuckDB and works similarly to other extensions. To be specific, the work we…

The nature of UI as an extension is somewhat hard to understand, since its installation method differs from other extensions. Even core ones. Some extensions autoload, some require INSTALL query, and this one has its own special builtin query. It at least feels more ingrained than other extensions by its user experience.

Then there's the (to me) entirely new feature of an extension providing a HTTP proxy for external web service. This part could have been more prominently explained.

Edit: the OP states that "built-in local UI for DuckDB" and "full-featured local web user interface is available out-of-the-box". These statements make me think this feature comes with the release binary, not that it's an extension.

To clarify my point: for me it's not the possible confusion of what this plugin does or how, but what this collaboration means for the future of DuckDB's no-cost and commercial usage.

Re: The DuckDB Local UI

#76
post #32

I suggest https://perspective.finos.org/ for data viz to be built in. We use DuckDB paired with Perspective for client-side BI use case, and it's been great.

Glad you dig it! Check out our pro version to - it also support DuckDB, Python/Pyodide and more! https://prospective.co

Wow that's really cool! Part of my PhD thesis was about writing stable treemapping algorithms for temporal data. The idea being that you want your treemap cells not to fly around like what I'm seeing in your demo, but to remain more or less in the same position without sacrificing too much on the cells aspect ratios. We've come up with a pretty effective and fast method to do that, check out the paper and a demo down below. Maybe we could even do a collaboration to get this implemented in perspective.

https://github.com/EduardoVernier/eduardovernier.github.io/b...

https://youtu.be/Bf-MRxhNMdI?list=PLy5Y4CMtJ7mKaUBrSZ3YgwrFY... (see the GIT method)

Re: The DuckDB Local UI

#77
post #24

Earlier quoted context omitted.

I'm a bit out of the loop here, but what's the use case for DuckDB?

for the average developer I think the killer feature is allowing you to query over whatever data you want (csv, json, parquet, even gsheets) as equals, directly from their file form - can even join across them

It has great CSV and JSON processing so I find it's almost better thought of as an Excel-like tool vs. a database. Great for running quick analysis and exploratory work. Example: I need to do some reporting mock-ups on Jira data; DuckDB sucks it all in (or queries exports in place), makes it easy to clean, filter, pivot, etc. export to CSV

If you're developing in the data space you should consider your "small data" scenarios (ex: the vast majority of our clients have < 1GB of analytical data; Snowflake, etc. is overkill). Building a DW that exists entirely in a local browser session is possible now; that's a big deal.

Re: The DuckDB Local UI

#79

Earlier quoted context omitted.

How do you compete with Supabase ? Do you have a built in authentication system? Anything like edge functions. I've been trying to build a small card game with Supabase and I'm sorta stuck...

Supabase IMO sits in the middle of the curve between Firebase and PocketBase, not really the same use case as DuckDB & MotherDuck.

Motherduck has pretty generous free usage limits, I figured it was worth asking...

Re: The DuckDB Local UI

#80

Earlier quoted context omitted.

I'm a bit out of the loop here, but what's the use case for DuckDB?

DuckDB is mind blowingly awesome. It is like SQLite, lightweight, embeddable, serverless, in-memory database, but it's optimized to be columnar (analytics optimized). It can work with files that are in filesystem, S3 etc without copying (it just looks at the necessary regions in the file) by just doing `select * from 's3://....something.parquet'`. It support automatic compression and automatic indexing. It can read j…

Wow... sounds pretty good... you should be doing PR for them... I might give it a try, sounds like I should.
Post reply on HN