Hacker News: hamilton

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 19:03:31 +0000

We do have plans. It's a question of effort, not business / philosophy.

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 18:13:53 +0000

it can, but it doesn't format. You can even run the ast!

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 17:24:35 +0000

Obviously one advantage of SQL is everyone knows it. But conceptually, I agree. I think [1]Malloy is also doing some really fantastic work in this area.

This is one of the reasons I'm excited about DuckDB's upcoming [2]PEG parser. If they can pull it off, we could have alternative dialects that run on DuckDB.

[1] https://www.malloydata.dev/ [2] https://duckdb.org/2024/11/22/runtime-extensible-parsers.htm...

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 16:46:28 +0000

Definitely something we want too! (I'm the author / lead for the UI)

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 16:31:43 +0000

I agree; one thing that is neat about Instant SQL is for many reasons, you can't do this with in any other DBMS. You really need DuckDB's specific architecture and ergonomics.

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 16:30:07 +0000

Great feedback! Thanks. We agree w/ the red errors. It's not helpful when it feels like your editor is screaming at you.

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 16:28:44 +0000

You should read the post! This is what the feature does.

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 15:30:38 +0000

Can you say more? Where does it error out? Sounds like a bug; if you could post an example query, I bet we can fix that.

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 15:19:11 +0000

What about it is bizarre?

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 15:13:57 +0000

Me too (author of the post here). In fact, I was watching a seasoned data engineer at MotherDuck show me how they would attempt to debug a regex in a CTE. As a longtime SQL user, I felt the pain immediately; haven't we all been there before? Instant SQL followed from that.

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 15:08:54 +0000

Correct. We only enable fast previews for SELECT statements, which is the actual hard problem. This said, at some point we're likely to also add support for previewing a CTAS before you actually run it.

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 15:07:11 +0000

You can use any variation of DuckDB valid syntax that you want! I prefer to put from first just because I think it's better, but Instant SQL works with traditional select __ from __ queries.

New comment by hamilton in "Instant SQL for results as you type in DuckDB UI"

hamilton — Thu, 24 Apr 2025 15:04:32 +0000

Indeed, we are! We worked with DuckDB Labs to add the query_location information, which we're also enriching with the tokenizer to draw a path through the AST to the cursor location. I've been wanting to do this since forever, and now that we have it, there's actually a long tail of inspection / debugging / enrichment features we can add to our SQL editor.

New comment by hamilton in "The DuckDB Local UI"

hamilton — Thu, 13 Mar 2025 12:17:11 +0000

ftr I'm still on X & posting! https://x.com/hamiltonulmer

New comment by hamilton in "The DuckDB Local UI"

hamilton — Wed, 12 Mar 2025 16:54:06 +0000

True; at the moment the UI is not open source. We've talked about releasing the Column Explorer as a standalone component, but haven't been able to prioritize it yet. We'd like to!

New comment by hamilton in "The DuckDB Local UI"

hamilton — Wed, 12 Mar 2025 16:47:18 +0000

(I designed and built the Column Explorer feature)

Observable's column summary feature is very nice! But I do think there's a very common lineage around these kinds of diagnostics which motivated both Observables and ours. See Jeff Heer's profiler paper[1] for more.

I'm very passionate about this area because I think "first mile problems" are underserved by most tools, but they take the longest to work out.

We had to do some gnarly things[2] to make this feature work well; and there's a lot of room to make it scale nicely and cover all DuckDB data types.

[1] http://vis.stanford.edu/papers/profiler [2] https://motherduck.com/blog/introducing-column-explorer/

New comment by hamilton in "TinyBase: A JavaScript library for structured state"

hamilton — Mon, 17 Jan 2022 15:14:50 +0000

love this. I similarly use immer for just about every svelte project I build & maintain.

New comment by hamilton in "Rich Harris joins Vercel to work on Svelte full time"

hamilton — Thu, 11 Nov 2021 16:53:11 +0000

I find that Svelte is the most "jQuery-friendly" of the frameworks. I can easily add a single Svelte component back into other wise static pages without requiring anything other than a simple build tool to output the JS + css. It's really the best of both worlds – sprinkle it in where needed, or go whole-hog.

New comment by hamilton in "Show HN: Jupystar – Run any Jupyter notebook in the browser"

hamilton — Sat, 21 Nov 2020 16:42:39 +0000

So great to see folks utilizing Pyodide, the WASM scientific python stack my Mozilla colleagues put together. The creator, Mike Droettboom, wrote a Mozilla Hacks post about it a while back:

https://hacks.mozilla.org/2019/04/pyodide-bringing-the-scien...

New comment by hamilton in "Ask HN: What are your experiences with Svelte (JS framework)"

hamilton — Mon, 28 Oct 2019 18:26:40 +0000

Thanks for the link. Incidentally I have that same talk bookmarked. Though for the record, I have needed to render thousands of dom elements per second :)