hamilton

10 ms·

1.
by hamilton 23d ago
Indeed, OLAP cubes keep finding new life. The critical difference here is that there isn't a heavy query engine (just a Parquet reader) and a few http requests to pull from the cube. So it's light on the backend and light on the f
2.
by hamilton 23d ago
I think it depends on (1) customer expectations for freshness and (2) scale (both for the cubes and for the customer data in toto). There are many types of customer facing dashboards where giving "live data" is a bad idea for them
3.
by hamilton 23d ago
It's a good question. In a sense, the cube is caching, just materialized ahead of time instead of memoized on demand. A result cache still needs a live database behind it for misses; the cube has no misses, since every question the da
4.
by hamilton 23d ago
Agreed, for a public demo like this one, GitHub Pages would work great (or any host that speaks HTTP range requests with CORS). I used R2 partly because I wanted to see how it behaved, and partly because the real use-case doesn't fit P
5.
by hamilton 1y ago
We do have plans. It's a question of effort, not business / philosophy.
6.
by hamilton 1y ago
it can, but it doesn't format. You can even run the ast!
7.
by hamilton 1y ago
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.
8.
by hamilton 1y ago
Definitely something we want too! (I'm the author / lead for the UI)
9.
by hamilton 1y ago
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.
10.
by hamilton 1y ago
Great feedback! Thanks. We agree w/ the red errors. It's not helpful when it feels like your editor is screaming at you.
11.
by hamilton 1y ago
You should read the post! This is what the feature does.
12.
by hamilton 1y ago
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.
13.
by hamilton 1y ago
What about it is bizarre?
14.
by hamilton 1y ago
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 b
15.
by hamilton 1y ago
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.
16.
by hamilton 1y ago
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.
17.
by hamilton 1y ago
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
18.
by hamilton 2y ago
ftr I'm still on X & posting! https://x.com/hamiltonulmer
19.
by hamilton 2y ago
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!
20.
by hamilton 2y ago
(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 Jef
21.
by hamilton 5y ago
love this. I similarly use immer for just about every svelte project I build & maintain.
22.
by hamilton 5y ago
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&
23.
by hamilton 6y ago
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&#x2
24.
by hamilton 7y ago
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 :)
25.
by hamilton 7y ago
Oh, great! Thanks for the link. I had it on my to-do list to try something similar to what you did. Glad to learn from someone else's exploration.
26.
by hamilton 7y ago
I've posted before about my experience with svelte ( https://news.ycombinator.com/item?id=20338175 ). Will try to reiterate a few of them here. I've been using it internally at my current job to great effect since M
27.
by hamilton 7y ago
From experience building more complex apps in Svelte, I can say that this has not been my experience, & doesn't accurately depict React in practice. Three aspects that make it really killer – a really great story for handling app &
28.
by hamilton 7y ago
Unfortunately not – they're all private, internal views at the moment. I do hope to clean up some of my components and write something about some of the cool workflow aspects I've been able to unlock. In the meantime, I would reco
29.
by hamilton 7y ago
As someone who has built a number of data products w/ React, I decided to give Svelte a try a few months ago. At this point I am using it on some internal projects to great success & ease and probably wouldn't go back to React
30.
Mozilla Research Grants 2019 – call for proposals(mozilla-research.forms.fm)
1 points by hamilton 7y ago|0 comments

More ›