Linux and plethorization
Why is it that Linux distros divide and multiply? And do we have a better name for how and why that's done than, say, "forking"?
For the many years I've been writing about Linux, it has always amazed me that no distro ever wins, in the sense that it vanquishes many opponents in the marketplace. Instead success breeds other successes through forks, variants and derivations by other labels.
In explaining how this works recently, I used the verb "plethorize" and the noun "plethorization", both derived from the noun plethora, which comes to us from Greek via Latin. In the Greek it meant "fullness". As synonyms Wiktionary lists "(excess, abundance): glut, surfeit, superfluity, slew". So I suggest that plethorize would mean to create abundance, and plethorization would be a generalized process of doing that.
What makes Linux an ideal example of plethorization is its abundantly useful nature. It lends itself toward endlessness in the ways it gives you to try, fail, retry, succeed and improve. That's why it's hard to fight against it. Whacking at it becomes like the sorcerer's apprentice taking an ax to his magic broom. Each splinter becomes a new magic broom. The difference with Linux is that all the magic brooms go off in their own directions, try different approaches, and improve in their own ways, all along sharing the results with everyone who is interested.
Anyway, here's the beginning of an experiment. On Google today we see these search results:
I used the + to force exact returns.
It'll be interesting to see how those change.
Doc Searls is Senior Editor of Linux Journal
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Django Models and Migrations
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Home Automation with Raspberry Pi
- Shashlik - a Tasty New Android Simulator
- Huge Package Overhaul for Debian and Ubuntu
- KDE Reveals Plasma Mobile
- Embed Linux in Monitoring and Control Systems
- diff -u: What's New in Kernel Development