BrokeIt - Trending Repos · All episodes: ↗

uv's Lightning Speed, CLI-Anything, Appwrite

2026-11-20 · 9 min

Listen · Apple Podcasts Listen · Spotify

Stories covered

Transcript

Intro

Sam: A Python package install, with a warm cache, in under ten milliseconds.

Kai: I'm Kai.

Sam: And I'm Sam.

Kai: And this is Trending Repos for Friday, November 20th, 2026! We've got three huge projects lined up for you today.

Sam: Huge is one word for them. Let's see if they hold up.

Kai: On deck: a project that claims to be a drop-in replacement for Python's pip... but a hundred times faster.

Sam: We're also looking at a tool that promises to wrap any piece of software in a command-line interface, just for AI agents.

Kai: And we'll round things out with a self-hosted, open-source cloud platform that wants to be the backend for your next big idea.

astral-sh/uv

Kai: Alright, let's dive in. We're talking about Python packaging... again. But this one feels... different. It's `uv` from astral-sh.

Sam: From the same team behind Ruff, the super-fast Python linter. So they have a track record with Rust and Python tooling.

Kai: Exactly. It's a Python package and project manager, and they're not kidding when they say it's fast. They claim it's 80 to 100 times faster than `pip` and `pip-tools`.

Sam: I see claims like that all the time. 'Faster' often means 'cuts corners'. What's the catch, Kai?

Kai: The catch is... I'm not sure there is one? It's written in Rust, uses parallel I/O, and has a global package cache. So once you download a package, you never download that version again, across any project.

Sam: Okay, a global cache makes sense. That explains the warm-cache install time you teased. But what about a cold cache? Or a complex dependency graph?

Kai: Still blazing fast. Installing CPython from a cold cache takes about 8 seconds with `uv` versus almost 4 minutes with `pip` and venv.

Sam: That's... significant. But they call it a 'drop-in replacement'. That's a bold promise in the Python packaging world. Does it support `pyproject.toml`? Does it handle lock files? What about private indexes?

Kai: Yes, yes, and yes. It reads `pyproject.toml`, generates and uses lock files like `pip-tools`, and supports private registries. You literally just type `uv pip install` instead of `pip install`.

Sam: Okay, so you do have to change your commands. And I'm sure there are edge cases. There always are. Something, somewhere, is going to break.

Kai: Maybe, but imagine your CI pipeline finishing in 30 seconds instead of 10 minutes. That's a game-changer. So, what can you build with this?

Sam: Okay, let's hear it. How does a builder use this today?

Kai: It's simple: you swap it in to speed up package installation and virtual environment management. To get started, their README has a curl or PowerShell script you can run.

Sam: Piping curl to shell. My favorite secure installation method.

Kai: They offer other methods! But yeah, from there, you just run `uv venv` to create an environment and `uv pip install` to add packages. Go check out the repo yourself: astral-sh/uv. The speed is real.

Sam: I'll admit, for CI costs alone, this could be huge. Faster builds mean cheaper builds. But I'll wait until I see how many 'works with `uv`' badges start popping up.

Kai: Don't wait too long, you might miss it. [laughs]

HKUDS/CLI-Anything

Sam: Alright, next up. Let's get into this whole 'agent-native' craze. We're looking at a repo from HKUDS called CLI-Anything.

Kai: Right! Their tagline is 'Making ALL Software Agent-Native'. The idea is to take basically any app—even complex GUI ones—and wrap it in a command-line interface so an AI agent can use it.

Sam: Automatically generate a CLI for a GUI app? How does that even work? Is it using accessibility APIs? Screen scraping? It sounds... fragile.

Kai: You build a tool-specific 'control adapter'. It observes how the app works and maps actions to commands. So you could tell an agent, 'Crop this image and apply a filter,' and it could actually drive Photoshop to do it.

Sam: Okay, that sounds like a ton of work to define that adapter. And what happens when Photoshop updates and a button moves? The whole thing breaks. You've just created a maintenance nightmare.

Kai: But think of the possibilities! You could connect your entire workflow to an agent. Code editors, database clients, design tools... anything. It's about giving agents hands.

Sam: It sounds like giving a toddler a wrench and pointing them at a jet engine. The interface has to be incredibly complex to expose all of a GUI's functions. The agent's context window would explode just trying to read the help text.

Kai: Well, they have a 'CLI-Hub' where people can share pre-built interfaces, so you don't have to start from scratch. They already have one for web browsing.

Sam: A CLI for a web browser feels more manageable than, say, Blender. The scope matters here. So, what's the builder angle? What can someone actually do with this right now?

Kai: You could build a wrapper for any tool, making it accessible to an AI agent. Think about some internal tool at your company. The repo has a 'Getting Started' guide that shows you how to initialize a new project for whatever software you want to wrap.

Sam: And then spend the next six months writing a 'control adapter'?

Kai: [laughs] Maybe! But hey, check out the repo, HKUDS/CLI-Anything. It's a fascinating—if ambitious—approach to solving that 'last mile' problem for AI agents.

appwrite/appwrite

Kai: Alright, our last project today is appwrite/appwrite. It's been around for a while, but it's really picking up steam lately.

Sam: Ah, the 'open-source Firebase alternative'. We've seen a few of these. What's Appwrite's hook?

Kai: Their tagline is 'The open-source cloud for agents & devs'. And it's a full backend in a box: you get auth, databases, storage, functions, hosting... everything you'd expect.

Sam: Okay, so it's a monolith. Nothing wrong with that if it's done well. Is it really a 'cloud' though? It's self-hosted, right? You're the cloud operator.

Kai: Correct. You run it yourself, which means no vendor lock-in and you control your data. It's all packaged as a set of Docker containers, so getting it running is surprisingly easy.

Sam: Easy to run, maybe. But what about scaling? Backups? Security updates? When you self-host, all of that is on you. That's the trade-off for 'no vendor lock-in'.

Kai: True, but they have SDKs for basically every platform you can think of: Web, Flutter, Apple, Android, Node, Deno, even Dart. It makes it incredibly fast to get a full-stack application off the ground.

Sam: I see it has over 45,000 stars. That's a lot of momentum. Is it organic, or are people just excited by the promise?

Kai: It seems pretty real. Their Discord is huge, and people are definitely building with it. So, let's talk about what a builder could do with Appwrite.

Kai: Honestly, you could build almost any app that needs a backend—a social app, an e-commerce store, a new SaaS product—but you host it all yourself.

Sam: And the first step?

Kai: Their docs show you how to get it running with a single Docker command. That's it. You can have a full backend running in minutes. The repo is appwrite/appwrite.

Sam: Running in minutes, managing for years. It's a powerful tool, but don't underestimate the operational overhead. It's not magic.

Kai: Okay, that's a wrap on the stories. Let's do a quick recap.

Sam: First, we had `uv`, a Rust-based Python package manager that's ridiculously fast, if you believe the benchmarks.

Kai: Then, CLI-Anything, an ambitious project to make any software controllable by AI agents. Ambitious being the key word.

Sam: And finally, Appwrite, a powerful, self-hosted backend-in-a-box that puts you in the operator's seat.

Kai: So, before we go... it's Friday. You deploying anything today, Sam?

Sam: I believe in read-only Fridays. The only thing I'm deploying is myself to a comfortable chair, far away from a terminal.

Kai: [laughs] Smart move. Maybe you can use some of that free time to install `uv` and see if you can actually get a package installed in under 10 milliseconds.

Kai: And that's our show! Thanks for listening to Trending Repos.

Sam: We'll be back on Monday with more projects. Have a great weekend. Try not to break production.

This show is made with AI: the hosts’ voices are synthetic and the scripts are AI-assisted. Every story links to its original source.