hakyll.esben-stien.name

The Case for Email Supremacy

June 4, 2026

This text was generated by multiple AI language models and compiled based on criteria and guidelines specified by Esben.

Email is the only communication system that got the fundamentals right from the start. Everything that came after—Slack, Teams, Discord, WhatsApp, iMessage—represents a regression in user agency, interoperability, and long-term viability.

Federated by Design

Email has no central authority. Anyone can run a mail server. Gmail users can email Protonmail users who can email self-hosted servers. This isn’t a feature that was added later—it’s the foundational architecture.

Contrast with modern alternatives:

The “network effect” that supposedly makes these platforms valuable is actually vendor lock-in dressed up as a feature.

You Own Your Data

Email sits in files on disk. Mbox, Maildir, EML—all readable with basic tools. You can grep your email. You can back it up with rsync. You can switch clients without losing anything. You can search 20-year-old messages with the same tools you use today.

The modern alternative:

Email’s “primitive” file-based storage is actually radical user empowerment.

Asynchronous by Default

Email assumes the recipient will read your message when they choose to, not when you demand it. There’s no “typing indicator” creating social pressure to respond immediately. No “read receipts” (unless you opt in). No presence status broadcasting your availability to the world.

Modern messaging tools have optimized for engagement—which means optimizing for interruption. Slack’s “someone is typing” indicator exists to keep you watching the screen. Read receipts exist to create obligation. Presence indicators exist to make you feel guilty for not responding.

Email treats your attention as yours to allocate. Modern tools treat it as a resource to capture.

Rich Formatting Without Lock-in

HTML email is contentious, but even plain text email supports:

And critically: all of this is standardized. RFC 5322 defines the format. RFC 2045-2049 define MIME. Any compliant client can read any compliant message.

Modern messaging has no standards. Slack’s blocks, Discord’s embeds, Teams’ adaptive cards—all proprietary, all incompatible, all designed to keep you inside their platform.

True Threading: Branching Conversations

Email threading isn’t just “group messages together”—it’s a directed acyclic graph. Any message can spawn multiple independent branches. A single email can receive three different replies that each become their own sub-conversations, handled by different people, on different timelines.

This maps to how complex discussions actually work:

Each branch lives independently. Each can be resolved, archived, or continued without affecting the others. The original context is preserved via References headers—you can always trace back to where a tangent started.

Slack and Teams? Linear. One channel, one timeline. If three sub-discussions emerge, they either interleave chaotically in the same channel, or someone creates three new channels (fragmenting context), or people try to use “threads” that are second-class citizens bolted onto a fundamentally linear model.

Email’s threading model was designed for the reality that conversations branch. Modern platforms were designed for the simplicity of a chat room.

Survives Platform Death

How many messaging platforms have died? AIM, MSN Messenger, Google Talk, Google Wave, Google Hangouts (classic), Google Allo, Facebook Messenger for Desktop (original), Skype for Business, HipChat, Yahoo Messenger, ICQ (for practical purposes), BBM, Path, Yik Yak, Vine (for DMs), and dozens of others.

Every one of those deaths meant lost conversations, lost contacts, lost history.

Email from 1995 still works. Your SMTP server from the 90s could still send mail today (protocol hasn’t broken). Messages stored in mbox from 2001 open fine in 2025.

The protocols and formats have remained stable for decades. How many chat platforms will exist in their current form in 2035?

No Algorithm Deciding What You See

Email arrives in your inbox in chronological order. There’s no algorithm deciding you should see this promotional email before that critical work message. No “engagement optimization” hiding messages you haven’t interacted with. No “relevance scoring” burying conversations.

Your filters and rules are yours. Sieve, procmail, your client’s rules—you control the logic. The system does exactly what you tell it to.

Slack has “All Unreads” which shows some things but not others. Teams has “Activity” which surfaces what Microsoft thinks matters. Gmail has “Primary/Social/Promotions” which trains you to ignore categories. The platforms have decided they know better than you what you want to see.

LLM-Native

Email’s structure—headers, quoted text, clear message boundaries—is perfectly suited for LLM assistance. Each message is a self-contained document with metadata. The threading structure provides context. The asynchronous nature means there’s no pressure to respond before you’ve had time to think (or have an LLM help you think).

What LLM-assisted email enables:

The open, text-based, file-stored nature of email means you control the LLM integration. Your local LLM, your prompts, your rules. No platform deciding which AI features you get access to or what they cost.

Slack’s AI? Microsoft’s Copilot in Teams? You pay what they charge, use what they provide, under their terms. Your email workflow? Integrate whatever tools you want, running wherever you want, with whatever models you choose.

Email is a protocol. Protocols don’t have business models. That’s why email will integrate with whatever comes next, while proprietary platforms will demand you pay for their version of it.

Email is legally recognized as business communication. Courts accept email as evidence. Retention policies are built around email. Discovery processes know how to handle email.

Slack messages in court? It’s a mess. WhatsApp “disappearing messages” as legal record? Problematic. The entire regulatory infrastructure (GDPR, HIPAA, SOX compliance) understands email.

This isn’t just bureaucratic inertia—it’s because email has properties (timestamps, headers, routing information, cryptographic signatures) that make it verifiable in ways that proprietary platforms don’t.

Identity Without Intermediaries

Your email address can be your own domain. bob@smith.com is controlled by Bob Smith, not by a platform. If Gmail bans you, you can take bob@smith.com to another provider. The address—your identity—is portable.

Your Slack handle? Your Discord username? Your Teams account? All exist at the pleasure of the platform. One algorithmic false positive, one policy change, one acquisition, and your identity vanishes.

Email allows identity self-sovereignty. Modern platforms require identity tenancy.

Encryption That You Control

PGP/GPG is imperfect, but it exists and works. S/MIME is enterprise-friendly. Both let you hold the keys. Neither requires trusting the transport layer.

“But WhatsApp has end-to-end encryption!” Yes, with keys managed by WhatsApp, in an app controlled by WhatsApp, with metadata visible to WhatsApp, and backup encryption they can (and do) compromise when convenient for law enforcement.

Email encryption means: I hold my private key. You hold yours. The message is encrypted on my device, decrypted on yours. No intermediary can read it, ever, even with a court order—because there’s no intermediary that has the keys.

Scales Down to One Person

You can run your own email server. It’s not trivial (spam reputation is hard), but it’s possible. One person can have a complete, functioning email system.

Running your own Slack? Running your own Discord? Running your own iMessage? Impossible by design. These systems require central infrastructure operated by the vendor.

Email’s decentralization means it can exist at any scale—from a single Raspberry Pi serving one family to Google’s infrastructure serving billions. Modern platforms only exist at scales that justify their business model.

The Counter-Arguments, Addressed

“Email is too slow for real-time collaboration.” Real-time collaboration is valuable, but it’s a feature that can be added to email workflows (chat is fine for ephemeral discussion). The problem is when real-time becomes the only mode. Email preserves the option for asynchronous communication; Slack makes it uncomfortable.

“Email has spam.” Spam exists because email is open. The alternative to spam is a closed system where only approved senders can reach you—which is what corporate platforms provide. This is a tradeoff, not a flaw. And spam filtering has gotten remarkably good.

“Email threads are confusing.” Email threads are confusing when clients display them badly. The data model (In-Reply-To, References) is sound. Blame the clients, not the protocol.

“Young people don’t use email.” Young people don’t own houses either, and we don’t conclude that housing is obsolete. Network effects and onboarding friction explain adoption patterns. The technical and architectural advantages remain.

“Email is old.” TCP/IP is old. HTTP is old. Unix is old. DNS is old. Age, for infrastructure, is a feature. It means stability, accumulated wisdom, proven interoperability. “New” in communication platforms has meant “untested,” “proprietary,” and “subject to enshittification.”

Conclusion

Email isn’t perfect. It’s clunky, it’s been abused by marketers, it has real UX problems that decades of clients haven’t fully solved.

But email got the architecture right. Open protocols. Federated identity. User data ownership. Asynchronous defaults. True branching threads. Client diversity. Standards-based interoperability. And now: native compatibility with the LLM revolution, on your terms.

Every major messaging platform since has abandoned one or more of these properties in exchange for “engagement” (i.e., addiction), “seamless experience” (i.e., lock-in), or “modern design” (i.e., we control the interface you see).

The question isn’t why email is better than Slack. The question is: what would you be willing to give up to escape the proprietary platforms? Email asks you to give up nothing. The modern alternatives ask you to give up everything that matters for communication infrastructure: control, ownership, portability, and permanence.

Email is boring in the way that running water is boring. It just works, it works for everyone, and it will keep working after the current crop of VC-funded messaging startups have pivoted, been acquired, or shut down.