Post

We made "ball-point disposable computers" by committing three heresies: Killing user container images, running orchestration inside the VM, and backing disks with S3. The result? Instant boot, auto-sleep, and zero dockerfile misery. Machines are for servers; Sprites are for everything else. 🔗 ➡ 🧵

21/1/26, 5:35 pm0 reposts1 like

yoooooo 🤯

🔗 ➡ fly.io/blog/design-...

fly.ioThe Design & Implementation of SpritesSo that we may educate as well as horrify: the internals of our new Sprites execution platform.

Michael Lynch

@mtlynch.io

22 Jan

I've been experimenting with sprites, and I like the idea, but I've found a lot of friction with getting projects into a sprite and syncing changes back out. What's the recommended flow for cloning a private git repo, letting LLMs work, then pulling changes out? Anything better than magic-wormhole?