mootoday

AI of course

https://seaquel.app/

It's the SQL client I've always wished I had. It's a desktop app, but I made it work in the browser too thanks to DuckDB Wasm.

And now there's a skill to do just that.

https://cloudrouter.dev/

You don't need a vendor-locked solution for AI agents to work in their own isolated environments :-).

- https://sprites.dev - https://mise.jdx.dev - https://fnox.jdx.dev

Develop a small API that accepts a prompt, starts a sprite sandbox, and then you wait for the AI agent to open a pull request.

I developed that in less than a week and now my client owns the code, can customize it to their needs, and if they want to use a different compute environment, they can with minimal code changes needed.

https://seaquel.app

Month 2 of building the SQL client I've always wished I had.

One feature I'm especially proud of is the visual query builder. Drag & drop to build SQL queries.

There's also an entire SQL tutorial section for anyone who wants to learn or refresh SQL knowledge.

I built something similar after reading the blog post, based on sprites.dev.

A day of work to get the prototype working and a few hours the next day to allow multiple users to authenticate.

It's surprisingly simple.

After reading the article, I built a tool like that with sprites.dev. There's a websocket to communicate stdout and stderr to the client.

Web app submits the prompt, a sandbox starts on sprites.dev and any Claude output in the sandbox gets piped to the web app for display.

Not sure I can open source it as it's something I built for a client, but ask if you have any questions.

Yeah, I've noticed similar things with my projects. Hard to avoid these days I think.

Awesome, thanks for being an early adopter!

I got some great feedback already, so I'll continue building it out.

Roadmap: - Release binaries for Intel Mac, Linux, Windows - Add / test support for more database engines - Wrap up the LLM integration

Holidays are coming up, it may be a productive time haha

I'm sure everyone has their own tolerance for what is and isn't maintainable :). For me, not knowing what code exists, where it is, how it fits together, and stuffing it all in one main file feels like a recipe for trouble down the road. Sure, I could probably tell the LLM to split the main file into modules and ask it to refactor code etc.

However, from personal experience I'm a lot more efficient when I use LLMs to help with tedious, boilerplate-like code writing but I remain in control over structuring the project so it's maintainable by more than machines only.

I use LLMs every day to write tests for example, it's a massive time saving and I wouldn't want to write tests manually ever again.

Hey, I did not. As mcbetz mentioned, I tried vibe-coding and anything you see is generated by LLMs. He linked to my blog post where I summarized the journey.

ZenQuery looks nice, I like the focus on supporting regular files.

There we go, all set up!

https://github.com/WebstoneHQ/seaquel

It was frictionless to get everything up and running.

Communication between the frontend and backend is via an `invoke` method, easy as pie :).

It's not open source, but once I get the Apple developer stuff all done, I'll add an auto-update feature and open source it.

A database desktop client, built with Tauri & SvelteKit.

"But there are many already!" I hear the crowd exclaim.

I respond, "Yes, but..."

It's really something I want for myself. Lightweight, as fast as humanly possible, extensible via plugins (in fact the entire app is mostly plugins, with a small core to glue it together), and a tiny bit of LLM (call it AI if you wish) integration to ask questions about the database or generate/review queries.

That's how I feel about most visual database clients I've used over the years...

It's something I hear from many others too, hence my interest in trying to build an incredibly fast and lightweight product.

Thanks for your insights. What made you stop working on it?

The insomnia creator also has a Tauri http client now called Yaak(.app). A huge inspiration to work on my database client.

Thank you, I appreciate the in-depth opinion! I think Tauri with SvelteKit is going to be my first prototype, likely followed by gpui because I'm impressed by Zed which is built with gpui.

Also, TIL about PopOS, thank you!

I recently started to get an interest in writing a GUI with Rust. In particular, a database GUI.

Initially, I thought Tauri with Svelte. Then I learned about gpui (https://www.gpui.rs/) and I'm intrigued.

TIL about iced, which seems to have been around for a while.

Before I embark on building a prototype UI for my app with all three libraries, does anyone have hands-on experience they can share?

My personal favorite to keep an eye on is https://www.gpui.rs/.

It's what Zed(.dev) is based on. While not quite ready for prime time from what I understand, if Zed is the reference implementation, I'm sold!

I'm working on https://pipestack.dev, a workflow automation platform where you bring your own code - as Wasm Components.

Think n8n, but you bring your own code and optionally even your hardware to execute pipelines.

Ooooh... you just gave me an idea :). A TUI for http://todotxt.org/.

That way, there's no lock-in and people can easily use their existing todo.txt to try the TUI.

I'm looking for a TUI idea to explore Ratatui, so maybe this is it right here!

My bad, I'm looking for TUI ideas to build to learn Ratatui :).

Is there anything you'd like to do in a TUI but can't find a TUI that does it?

I'm a long-time SvelteFlow user and it has never disappointed so far :).

Lots of updates this year to reach parity with React Flow.

I came to post the same comment :-)!

I ended up reading the entire article and what SvelteKit does isn't exactly the same, you can't edit the site.

The use case for a single html file for me is to provide a local dev experience for my customers that mirrors production.

`my-cli dev` spins up the services needed for my platform, including the SvelteKit web app.

You can opt out of AI features in Zed [0].

[0] https://zed.dev/blog/disable-ai-features

Full disclaimer: I only scanned the article, but based on the title, SvelteKit does that with a single option "inline".

https://svelte.dev/docs/kit/configuration#output

Tell me it's early days without telling me it's early days...

hi (at) pipestack.dev should work

I'm heads down building a workflow pipeline builder that executes Wasm Components as part of individual nodes within the pipeline.

Think Zapier or n8n, but you either use existing processing nodes or upload your own code, written of course in any language that compiles to Wasm Components.

It's week 2 but it works and it's live at https://pipestack.dev

What I get is isolation, so I can run untrusted customer code as a Wasm component knowing it runs in a secure sandbox.

Also, scaling across clouds, edge, on-prem with minimal effort.

Another benefit I enjoy now is changing links between components at runtime. I can for example deploy v2.0.0 of a component and send traffic to it by simply updating a link - and reverse it should things break.

All that comes at a much lighter cost in terms of actual $, but also size (kilobytes/megabytes vs megabytes/gigabytes with Docker containers)

I hadn't really been interested in WebAssembly until I read about the component model and the fact that I can run Wasm components on the server.

That led me to wasmCloud[1]. As the article says, Wasm on the server isn't a winner yet, but it has a chance.

[1] https://wasmcloud.com