Building databases for agents @Supabase. Previously Founder/CTO @tursodatabase (acq'd by Supabase), @ScyllaDB. Author of "Latency" (https://xitter.cf/t.co/XWRFq71WaJ).
Espoo, Finland 🇫🇮🇪🇺
Joined January 2010
- Tweets11.1K
- Following1.2K
- Followers20.1K
- Likes19K
Pekka Enberg retweeted
I wrote a new blog post about MVCC in @tursodatabase . The post does not focus on one thing in the system but instead follows the life of a row. From birth up to ultimately its death turso.tech/blog/mvcc-row-lif….
Pekka Enberg retweeted
We will open new positions soon for the Turso team. If you have experience writing databases and want to help us shape the future of a world with billions of databases - let me know!!!!!
Is there anyone I know from @AnthropicAI to talk to about getting @tursodatabase enrolled to oss-scanner? github.com/anthropics/oss-sc…
Linus hacking on Linux kernel with Claude is all the validation you need that AI coding agents are also for systems programming.
Linus Torvalds Working On A Hefty Linux Kernel Improvement With Claude Code
Linux creator Linus Torvalds uses AI himself (Claude) for working on a huge perf improvement to the Linux kernel. And Claude to help draft a test program and commit message.
phoronix.com/news/Linus-Torv…
The @exedev integration in Splay is coming together pretty nicely. By building a template VM per project, you can create a new remote workspace in under 10 seconds!
I built this tool for myself back in April, when no agent development environment (ADE) supported Linux. I’ve used it every day since and kept improving it, so it felt like time to give it a proper name and a home: splay.sh
I’m also experimenting with remote sandbox support using @exedev. If you’re running coding agents on Linux, give it a try!
Nice! 👏👏👏
To secure open-source software, we’re launching OSS Scanner.
We’ll use our frontier models to periodically scan opted-in open-source projects for vulnerabilities, at no cost. Our reports will provide a proof-of-concept, explanation, and suggested fix.
anthropic.com/research/launc…
I am glad you liked the post, @kiwicopple, because knowing @glcst, there are many more such bangers to come now at @supabase!
@supabase has acquired @tursodatabase
i'm been a huge fan of the team and what they've built. we have big plans together. more to share in our keynote in a few hours
this is the tweet that convinced us they'll fit right in
xitter.cf/glcst/status/209307402…
I have a contrarian view on open source and AI. From my point of view, nothing of essence has changed. If you have an itch to scratch and send a patch, I’m happy to consider merging it. In fact, the barrier to entry is much lower now because maintaining the code change is cheaper over time with AI assistance. However, if you send a crappy patch or a massive PR, I will probably ignore you, just like I always did. Perhaps other maintainers always had a different approach?
Stages of grief about the effect of AI on open source.
Denial:
- AI code is slop! Nobody serious will use this.
- Open source will keep working exactly like it always has.
Anger:
- These AI slop PRs are ruining GitHub!
- Ban AI-generated code!
- If you close PRs, you're not open source anymore!
Bargaining:
- Okay, AI can write code, but only if a human reviews every line.
- Maybe adversarial AI review will make arbitrary external code intake safe again.
Depression:
- Wait, if code generation is basically free, what is a contribution anymore?
- Is GitHub-style open source culture just going away?
Acceptance:
- Open source is still open source, even if the contribution model evolves.
- Good issues, test cases, benchmarks, specifications, and ideas become the scarce inputs.
- Upstream may stop accepting arbitrary code while forking becomes much easier.
Bonus stage! Reconstruction:
- Projects redesign around maintainer-controlled agents, issue-driven development, stronger test/validation infrastructure, and new ways for contributors to earn trust.
I sometimes wonder why some open source maintainers feel overwhelmed with PRs these days. For me, if something looks fishy, I just close or ignore it, and for ones where I see genuine effort, it's trivial to ask Claude Code to fix up issues I see (simplify solution, add test, etc.), and force push to contributor branch. I find this an improvement over the slow review cycles we had pre-agents
Just like Claude Code, Codex keeps flagging local GPU lockup debugging as "security issue". But surprisingly enough, when I remind Codex what we're doing, it keeps going.
Deep dive from @Peristocles1 on how we made concurrent writes fast in @tursodatabase with group commit: turso.tech/blog/turso-group-…
Btw the idea was shamelessly stolen from @TylerFCloutier and the SpacetimeDB team
Pekka Enberg retweeted
Turso v0.8 is out!
Completementary @penberg's post, I deep dived into why our commit path wasn't scaling properly in v0.7 and what it took to achieve 500x lower tail latency.
Check out turso.tech/blog/turso-group-…
I always knew databases were sexy, but it's nice to get external validation from ChatGPT when asking it to draw a diagram of Turso: "We’re so sorry, but the prompt may violate our guardrails around nudity, sexuality, or erotic content."
Turso 0.8 is now out! In our benchmarks, it has up to 500x lower transaction tail latency and 7x higher concurrent write throughput than SQLite. turso.tech/blog/turso-0.8.0
I'm working on Turso 0.8 release blog post. Turns out @jussisaur likes @BenjDicken's balls (the animations) so much he wanted us to try out something too.