Every office network, every data center, and a surprising amount of factory-floor automation still runs on a technology that was sketched out in a memo more than fifty years ago. Ethernet was invented in 1973, and the story of how it got its name is one of the more charming footnotes in computing history.
A memo at Xerox PARC
In May 1973, a young engineer named Robert Metcalfe was working at Xerox's legendary Palo Alto Research Center (PARC), the same lab that gave the world the graphical user interface and the laser printer. PARC had a problem: it had built a room full of experimental personal computers, but no good way to connect them all to a shared laser printer and to each other.
Metcalfe wrote a memo describing a solution — a single shared cable that any machine could talk on, listening first to avoid talking over another machine, and retrying after a random delay if two transmissions collided. That collision-detection scheme, later formalized as CSMA/CD, became the beating heart of Ethernet. Metcalfe developed the working system together with his colleague David Boggs, and decades later, in 2022, Metcalfe received the Turing Award for the invention.
Why it is called "Ethernet"
The name is where the poetry comes in. For centuries, physicists believed light travelled through an invisible, all-pervading medium they called the luminiferous ether. The theory was eventually disproved, but Metcalfe borrowed the word as a metaphor: just as the old ether was imagined to carry light everywhere, his shared cable would carry data to every machine connected to it. The "ether" was the medium; the network was Ethernet.
It is a small reminder that good engineering names often come from good stories, not committees.
From a lab cable to a global standard
What makes Ethernet remarkable is not that it was invented, but that it never really got replaced. The original ran at under 3 megabits per second over a fat coaxial cable. Today the same fundamental idea, standardized as IEEE 802.3, runs at gigabit and multi-gigabit speeds over twisted pair and fiber, and it still uses the same 48-bit MAC address scheme Metcalfe's team helped popularize.
The strongest foundational technologies rarely get thrown away. They get refined, standardized, and scaled — which is exactly why a 1973 idea is still in the wall behind your desk.
Why Ethernet still matters for IoT
It is tempting to think of the Internet of Things as an entirely wireless world of Wi-Fi and cellular modules. But wired Ethernet remains the quiet workhorse of industrial IoT. On a factory floor, in a building-automation cabinet, or inside a piece of medical equipment, engineers often want connectivity that is deterministic, immune to radio interference, and capable of delivering power and data over a single run. Standards like Power over Ethernet (PoE) and the newer single-pair Ethernet are extending that reach right down to individual sensors.
For a team prototyping connected hardware, the practical takeaway is that choosing between wired and wireless is a real engineering decision, not a default. A sensor that must never drop a reading may belong on a cable; a mobile device clearly does not. Getting that choice right early saves a lot of pain later — something we spend a lot of time on in our IoT and embedded services.
Building connected products in the Philippines
For students and startups here building thesis prototypes and first products, the lesson from Ethernet is encouraging: the best-engineered ideas are the ones that stay simple enough to last. When we help teams take a concept from schematic to a working board, we care as much about picking robust, well-supported technologies as about clever features. A design that leans on proven standards is a design that will still work — and still be maintainable — years from now.
If you are working on a connected device and want a hand choosing the right networking approach, or turning a prototype into something manufacturable, get in touch with Fluidwire. We work from silicon to cloud, and we are always happy to talk shop about the history and the future of how machines talk to each other.
Top comments (0)