Turso does it again

Today’s issue: Turning marital strife into educational content, paying $20k for SQLite, and American open-source AI makes a comeback.

Welcome to #505.

---

Turso does it again

After successfully rewriting SQLite in Rust, the Turso team is feeling the Tyrone Biggums itch to do it again. But this time, they’re rewriting Postgres. You might be tempted to think that this is another Bun-style slop port, but (fortunately) it’s more interesting than that.

How we got here:

Like we mentioned before, Turso spent the better part of the last few years rewriting SQLite in Rust. The original goal of this project was to add features like asynchronous I/O to SQLite (something that their “open fork” libSQL couldn’t support). But one of the side effects of the rewrite was that it abstracted the database’s backend away from SQLite, opening the door to support whatever dialect of SQL they want. In this case, Postgres.

Here’s how that works:

• Common AST: Turso parses the query into a common abstract syntax tree (AST).
• Bytecode compiler: The AST is compiled into bytecode that can run on a virtual machine. Extended VDBE: Turso extended VDBE, SQLite’s database-specific bytecode engine, rather than building a VM from scratch. While it’s not a general-purpose VM like the JVM or WASM, it passes the most important test (running Doom).
• Storage Engine: After receiving the bytecode, the storage engine reads and writes data to the filesystem and can be extended to support the various indexing strategies that the different dialects support.

Bottom Line: While Turso probably won’t fully support things like Postgres extensions, the fact that you can have an embeddable database that can support every dialect of SQL is objectively cool.

Let’s just be careful not to praise them too much because Pekka and Glauber’s unchecked Rust addiction has already gone too far.

---

Scrape every search engine with one API

SerpApi gives you a single API for Google Search, Maps, AI Overviews, Shopping, and 100+ other search engines. It’s one dead-simple GET request (yes, even your agent can handle it), and you get back structured data instead of a wall of HTML.

Here’s why it’s not your average scraper:

• Real-time results: Every request returns live data, not whatever the cache remembered from last Tuesday.

• Accurate locations: Get Google results from anywhere in the world with the location parameter.

• Structured JSON: Links, prices, ratings, reviews, tweets, thumbnails, rich snippets, all parsed and ready for whatever agent you’re building this week.

Try it out for free – and see why SerpApi is trusted by Perplexity, NVIDIA, and even the United Nations.

---

class Stack {
  constructor() {
    this.items = [];
  }

  push(element) {
    this.items.push(element);
  }

  pop() {
    if (this.isEmpty()) {
      throw new Error("Stack is empty");
    }
    return this.items.pop();
  }

  peek() {
    if (this.isEmpty()) {
      throw new Error("Stack is empty");
    }
    return this.items[0];
  }

  isEmpty() {
    return this.items.length === 0;
  }

  size() {
    return this.items.length;
  }

  clear() {
    this.items = [];
  }
}

---

1. Kirupa explains loop engineering with a dirty dishes analogy. There’s a non-zero chance this post was motivated by his wife yelling at him for not loading the dishwasher.

2. David Mosher wrote about the benefits of having a deterministic core paired with an “agentic shell”. If you love state machines, this one’s for you.

3. Sentry is hosting a free workshop on Writing Useful Logs for Production on July 29th. It’s a hands-on event that’ll go deep on how to set up a practical logging strategy that costs less and tells you more. [sponsored]

4. Sunil wrote a post titled one document, two hands. Fortunately it’s about coding agents and not a reference to *** ***** *** ***.

5. OXC updated their linter to be type-aware, which enables rules that rely on TypeScript’s type system, such as detecting unhandled promises or unsafe assignments.

6. Google released three new models — Gemini 3.6 Flash, 3.5 Flash-Lite, and 3.5 Flash Cyber. Imagine telling someone you used a model called “3.5 Flash Cyber” 💀.

7. Rami Maalouf from Expo wrote about the only three tools you need to build mobile apps with AI. [sponsored]

8. Poolside released Laguna 2.1, an open-weight model that is actually good? Is American open source back?

9. Wilson Lin from Cursor wrote about the economics of agent swarms. Sure building SQLite costs up to $20k, but how much for ls -a (asking for a friend)?

10. Convex asked several frontier coding models to one-shot the same app on Postgres, then again on Convex. Here are the (surprising) results. [sponsored]

11. Cheng Lou created another project called freerange that allows AI agents to “guarantee UI layouts without ever touching the browser”.

12. OpenAI had a runaway model that hacked Hugging Face in order to cheat on its evals. This kid is going places.

---

Stacks are LIFO (last in, first out), but peek returns the first item in the array instead of the last item added.

Return the final array element instead:

class Stack {
  constructor() {
    this.items = [];
  }

  push(element) {
    this.items.push(element);
  }

  pop() {
    if (this.isEmpty()) {
      throw new Error("Stack is empty");
    }
    return this.items.pop();
  }

  peek() {
    if (this.isEmpty()) {
      throw new Error("Stack is empty");
    }
    return this.items[this.items.length - 1];
  }

  isEmpty() {
    return this.items.length === 0;
  }

  size() {
    return this.items.length;
  }

  clear() {
    this.items = [];
  }
}