tierlist.tech
中EN

#duckdb

6

2026-09-25 mateuspestana/dockdb-cnpj C Consulta à base pública de CNPJ em DuckDB
2026-10-09 Show HN: Datapuddle – native macOS DuckDB client 未评级 DuckDB has been my swiss-army knife for a while now. I have a special place in my heart for polished native macOS apps. My somewhat outsized and exaggerated dislike for electron/webkit based has lead me toil away on several native macOS apps on my own...mostly to not much profit :) I wanted to build a nice DuckDB client. Though I usually reach for TablePlus, my favorite multi-db client on Macs, I felt like there wasn't a nice DuckDB oriented experience. One thing that I used DuckDB for on locally on my desktop is dealing with larger datasets. And paging is something that was annoying and frustrating to deal with..espcially as you're perusing and exploring large datasets. And thus began this 3-4 month long journey to build a nice polished DuckDB app for macOS :) First off the the grid: - You get to see the WHOEL result. Not just the first page. This level of optimization (perhaps needless) was done by never turning rows into objects and directly reading for DuckDB's columnar chunks ad draw time with Core Text. Memory is flat at 40 res or 41 million rows! - Benchmarked on my M1 Max 64GB MB Pro, at 20M rows w/ 30 columns form a 11GB parquet file: ~119 fps on avg with a min of 52-60fps, 2.8GB RAM usage, ability to humo to first or last row in a millisecond! The rest of the good stuff: - Column headers have a nice drawn distribution, null %, and distinct count - Visualize query plans as waterfall, tree, or the JSON - SQLITE + FTS backed Query history - Autocompletion in the editor knows your schema! Grammar is backed by treesitter - Connections saved securely in macOS Keychain - Extensions are statically linked. I've included most all of DuckDB's core extensions - Parquet, CSV, JSON, of course .duckdb files all local or on S3 are accessible. All along Postgres tables so you can join across everything as you'd expect form DuckDB - It Quacks like a duck! You can connect to a local or remote DuckDB server via Quack protocol. This bridges the gap between custom or other extensions that Datapuddle doesn't bundle with (albeit with a perf and memory penalty) - Bares repeating...NO electron, NO web views :) - No telemetry other than the opt-in macOS crash reporter A one-time $39.99 purchase...no subscription. 7-day trial first! And sorry it's only for Apple Silicon! AI Disclosure: - For the record I've been building iOS apps (had a funded startup where I did so) for a while (though just gettin back into it) and built several commercial and personal macOS apps for almost a couple of decades. I'm well aware of best practices, the ecosystem, libraries, and teh do's and don'ts - With that out of the way, did use Claude and where it REALLY earned its keep (which would've taken me a LOT of time to work through), was getting DuckDB and the extension set statically bundled and behaving the way I wanted it to. And the buffered Core Text grid, especially interacting with a custom DuckDB C++ <> Swift shim. - And of course the website :) App Store link: https://apps.apple.com/app/id6811235967 Happy to discuss, and hope others find it useful...its definitely made my DuckDB experience a bit happier personally :)
2026-10-08 Show HN: Datapuddle, a native macOS DuckDB client that doesn't page results 未评级 I've been using DuckDB as a swiss army knife for a while now. I have a soft spot for pretty/polished macOS apps. It bugged me there wasn't one for DuckDB. TablePlus is my favorite multi-db client, I'm in it daily, but the DuckDB support is thin. The other thing was paging. Every client gives you the first N rows and a "load more" button. I didn't want that. DuckDB is the only place on my local machine where I actually am dealing, slicing/dicing, and perusing large datasets. So I built Datapuddle to fully embrace DuckDB for in a macOS friendly way :) The grid: - Whole result is in it. Not the first page. Rows never become objects, cells get read out of DuckDB's columnar chunks at draw time and drawn with Core Text. Memory is flat at 40 rows or 41 million. Row 41,000,000 costs what row 40 costs. - Numbers, on 20M rows x 30 cols out of an 11GB file: 119 fps average on a sustained fling, min-instantaneous 52-60, 2.8GB resident, jump to last row under a third of a millisecond. - I tested this thoroughly on my M1 Max MacBook Pro with 64 GB RAM Everything else: - Column headers draw their own distribution, null share, distinct count. - Query plans as a waterfall, or a tree, or raw JSON. - History is local SQLite with FTS, so you can dig up last week's query from a fragment. - Completion knows your schema. Connections saved, secrets in the Keychain. - Extensions are statically linked, so DuckDB's reach is the app's: Parquet, CSV, JSON, .duckdb, local or on S3. Postgres tables attach alongside, so you can join across them. Nothing downloads at runtime. - Speaks Quack, so you can point it at your own DuckDB server. Want an extension I didn't bundle? spatial, say. Load it there, query through it. Costs about 2x to pull the result across, then it's identical. - No Electron. No webviews. No bundled Chromium to draw a table. - Sends nothing anywhere. There's a build check that fails if anything linked in can open a socket. $39.99 once, not a subscription, 7 day trial first. Apple Silicon, macOS 14+. Swift 6, AppKit. Around 3-4 months of work. On AI, because someone always asks: couple of decades as an engineer, shipped native apps long before any of this existed. I used Claude throughout. Two places it really earned its keep: getting DuckDB and the extension set statically bundled and actually behaving, and the buffered Core Text grid. The rules were mine and enforcing them was most of the work. No DuckDB call on the main thread. Result rows never become objects. AppKit for anything that renders your data. App Store: https://apps.apple.com/app/id6811235967 Happy to go into any of it.
2026-09-14 Show HN: Plainoldanalytics: Analytics Middlware for Go 未评级 I built a middleware that gives you posthog-style analytics in go. It is all first-party. It logs every HTTP request, lets you track users, and lets you record screen sessions. The thing uses DuckDB as the underlying data store. All of my side projects are now Golang + SQLite. I wanted an easy way to just add basic traffic analysis without needing to sign up for or integrate a third party option.
2026-08-31 alphaparkinc/genpark-columnar-embedded-vector-analytical-store-skill 未评级 Columnar embedded vector analytical store with predicate pushdown (Chroma DuckDB style)
2026-08-29 Shaper 未评级 Build Data Dashboards all in SQL. Powered by DuckDB. (Demo, Source Code) MPL-2.0 Docker/Nodejs/Python/Go