Hacker News Reader

Bread is legacy food. Beer is legacy drink. I feel like that about sums it up.

This sums up nothing. (You could go as far as saying that our own bodies are legacy systems. So what? What does that have to do with anything?)

> What does that have to do with anything?

It means that "legacy" is meaningless if it can be applied so so many other things.

Semantics are contextual, and your legacy bread / legacy software parallel doesn't convince me. Is it a precise term? no, but most ppl here will have a good idea of what it means.

Legacy is any code you wrote before lunch.

In their defense email is pretty inherently insecure with metadata and message subjects always leaking even when message bodies are encrypted.

The fire and forget model is also a big contributor to spam. If email were invented today I imagine it would look more like an E2E system that put the storage burden on senders.

Before ditching SMTP/etc, we'd need something to replace them.

TMTP (my work) is a candidate. More at https://mnmnotmail.org/