debba

hace 8 díasdiscuss

Author here, I build a database client so I'm obviously biased toward 'tooling solves this', happy to be challenged on that.

debba

el mes pasadodiscuss

> Author here. I maintain Tabularis, the open-source client the post is about, so obviously I have a horse in this race. > > The part I'd most like to be challenged on: I claim the account/cloud trend in database clients is a funding-model artifact rather than a user need. The counterargument I keep hearing is that team workspaces and synced query history are genuinely valuable, and we just don't ship them. That's true — we don't, and the post lists what local-first costs us. > > One thing I checked before writing this because I knew someone here would: the only autonomous network call the app makes is the Tauri updater hitting GitHub releases. No telemetry, no crash reporting. The code is on GitHub if you want to verify.

debba

hace 3 mesesdiscuss

Cannot see it in Codex CLI

debba

hace 5 mesesdiscuss

Author here. Happy to answer questions.

The main thing in this release is a plugin system for database drivers. The short version: plugins are standalone executables that Tabularis spawns as child processes and talks to over JSON-RPC 2.0 on stdin/stdout.

I looked at dynamic libraries first but the cross-language ABI story is painful and would have locked plugin authors into Rust (or at least a C-compatible interface). The stdin/stdout approach means you can write a driver in whatever you want — the only contract is the JSON-RPC protocol. It also gives you process isolation for free, which matters when you're dealing with database drivers that can have their own native dependencies and failure modes.

The tradeoff is some serialization overhead per call, but in practice you're always waiting on network or disk anyway, so it hasn't been an issue.

First plugin out is DuckDB. I kept it out of core because of its binary size, but it's the database I get asked about most, so it felt like the right first target.

One thing I'm still thinking through: whether to pull the built-in drivers (MySQL, PostgreSQL, SQLite, MariaDB) out of core entirely and treat them as first-party plugins. It would make the core much leaner and the architecture more consistent, but it adds friction on first install. Currently leaning toward a setup wizard approach. Curious if anyone has dealt with a similar tradeoff.

The plugin guide and protocol spec are in the repo if you want to build one: https://github.com/debba/tabularis/blob/main/plugins/PLUGIN_...

debba

hace 5 mesesdiscuss

https://github.com/debba/tabularis

I’m working on tabularis, a lightweight desktop database management tool designed for developers. It provides a modern interface for managing MySQL/MariaDB, PostgreSQL, and SQLite databases through a native desktop application. Built using Tauri v2 (Rust backend) and React 19 (TypeScript frontend), it offers native performance while maintaining the flexibility of web technologies.

debba

hace 9 mesesdiscuss

My project is: https://github.com/debba/storytel-player

debba

hace 9 mesesdiscuss

I built a desktop app for Storytel using Electron and React

Since Storytel doesn't have an official desktop application, I developed one using Electron to fill that gap.

The app provides a native desktop experience for listening to audiobooks and reading ebooks from Storytel on your computer.

Key features:

    Native desktop application for Windows, macOS, and Linux

    Can also be used as a web app

    Built with Electron for cross-platform compatibility

If you're a Storytel user who prefers a dedicated desktop app over the browser, feel free to check it out!

Submissions

Nobody Reads the SQL Anymore

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

[untitled]

Show HN: I got tired of writing Pandas scripts just to JOIN two CSV files

Show HN: Tabularis – DB GUI where drivers are JSON-RPC executables

comments