The case for language-native software

Rob Englander makes a simple argument: most apps still run on the old model of files, folders, and databases. LLMs don't. They speak in context windows, embeddings, and vector stores. The apps that survive this shift will be built around that reality, not bolted onto it.

The old stack — SQL tables, REST APIs, JSON payloads — is still fine for CRUD. But it's the wrong default for anything that needs to reason, search, or summarize. If your app's core job is understanding language, build on vector stores and context windows from day one.

This isn't a thesis about LLMs replacing SQL. It's about choosing the right foundation for the job. The apps that get this right now will have a real advantage when everyone else is retrofitting.

Why this matters for us: la gente who build tools for our communities need to pick foundations that actually work for how we use them — not bolt an LLM onto a 1990s database and call it smart.