tabularis
/blog/#deep-dive
AllReleasesAIPluginsCommunityOpen SourceUX & UI#deep-dive

6 posts tagged with #deep-dive

Aug 23, 2026, 13:32·13 min read·#ai

Code generation was only the beginning. Software development is becoming a loop

Tabularis Web touched 1,040 files and moved a desktop database client behind a second transport. This is how I managed it as 48 verified tasks, and why AI development is moving from prompts toward loops.

Read article →

More in #deep-dive

Andrea DebernardiAndrea Debernardi
Aug 12, 2026, 10:00·9 min read

We Accidentally Ran One SQL Script Across Multiple Database Connections

Run All looked like a UI feature. Underneath, it fanned one SQL script into parallel pool checkouts. The statements succeeded, the session state disappeared, and a parent-child import silently produced missing and duplicated rows.

Andrea DebernardiAndrea Debernardi
Jul 30, 2026, 08:52·10 min read

The Rust stack inside a ~15 MB installer

Two database stacks, several TLS verification paths, two SSH clients, a hand-written float16 decoder, and the vendored OpenSSL that refuses to leave: a guided tour of the fifty-odd top-level Rust dependencies behind Tabularis's compact installers — the other half of last week's Tauri story.

Andrea DebernardiAndrea Debernardi
Jul 27, 2026, 11:48·12 min read

Visual EXPLAIN beyond the app: one engine, multiple hosts

Visual EXPLAIN began inside the desktop app. Extracting it produced an npm package and an online visualiser, but also a public API, two release schedules, and a repository question I have not answered yet.

Andrea DebernardiAndrea Debernardi
Jul 22, 2026, 09:40·11 min read

Why I chose Tauri, and what it cost me

A database client is a systems program with a UI problem. That is why I chose Tauri over Electron and native. After six months and 64 releases, here is the part the framework comparison charts leave out.

Andrea DebernardiAndrea Debernardi
Jul 14, 2026, 17:43·12 min read

Optimizing a Virtualized React Grid: 3,420 Formatter Calls Down to 90

The Tabularis data grid was already virtualized, but wide tables still took 29 ms of React render work per scroll tick. The bottleneck was the visible rows, not the total row count.

Star on GitHubJoin Discord

Quick searches

↑↓ navigate↵ openEsc closeSearch by Orama