I’ve had very good experience with it last year. I used it at large scale with data that had been in iceberg previously and it worked flawlessly. It’s only improved since. Highly recommend.
I use them both depending on which feels more natural for the task, often within the same project. The interop is easy and very high performance thanks to Apache Arrow: `df = duckdb.sql(sql).pl()` and `result = duckdb.sql("SELECT * FROM df")`.
Data inlining is also currently limited to only the DuckDB catalog (ie it doesn't work with Postgres cataglogs)[0]. It's improving very quickly though and I'm sure this will be expanded soon.
I've always wished that there was an option to whitelist certain area codes. I've had the same number for 20 years, and now live in a different part of the country. I get very little spam from local area codes -- but a ton spoofing my phone number's area code. Sending all calls all those calls to voicemail while continuing to ring for local would be the right balance (kids' school, doctors office, etc...).
I thought my ThermoWorks Signal had a dead/defective battery after trying to charge it on a standard USB power adapter. Device booted up and and functioned fine, except the battery wouldn't charge. Plugged it into the provided adapter and it started charging again.
Thanks for the PSA, I'll be sure to get that adapter off my kitchen counter right away!
I’ve been meaning to find time to get ruff-lap working on Doom Emacs side by side with pyright. Is anyone who’s already managed to get it working willing to share their config?
Perhaps as a profit center to the tea industry. Most tea bags contain the grades of tea that can't be sold in the more expensive loose leaf form. Basically leaf fragments and dust. That material would otherwise be a waste product.
I’ve been using it to great effect for the last year or so. It really is a breath of fresh air. In my case, I’m using a Django backend, but there are lots of successful folks using other backend stacks as well so choose what you know best.
The book is a really quick and easy read. It’s pretty eye opening how productive, and effective, htmx can be with so little magic.
Ideally you’d used Parquet or ORC if querying from Athena/Trino/Presto. Since they are columnar formats you will enjoy considerably faster queues and lower query costs for most query patterns other than “select *…” since the query engine can just retrieve the columns needed for your query instead of the entire row.
Also, I recently started looking into olake[0] to serve the same purpose. What would you say differentiates Streambed?
[0] https://github.com/datazip-inc/olake