Comparing hard and soft infrastructure
It turns out that hard infrastructure is softer than the name suggests. This is good, since I want to make the case that both LInux and the Net are forms of infrastructure no less legitimate than water, electricity, roads, sewers and waste collection.
Understanding Infrastructure was my first posting on this subject. This is my second. More will come.
So far I've arranged my findings in the forms of photo essays. Here's one on sidewalk signage in Cambridge. Here's one of Boston on the day of its huge annual Boston Marathon. And here's one on the Minuteman Bikeway that runs from Cambridge to Lexington.
Here are my main provisional conclusions, so far:
- Infrastructure is natural. That is, we try to make it as additional to nature as possible. It sometimes improves on nature, but more often serves as an adjuct to it, altering it in some way, always for practical purposes.
- Infrastructure is patchy. In computing terms, we patch and debug it all the time. Even terminology changes. CATV becomes COMS becomes BROADBAND, all on a series of manhole covers. Sidewalks of brick are torn up and laid down again, over and over. Asphalt streets are patchworks of exposed and buried culverts, piping and conduit.
- Branding is interesting, but eventually anachronistic.Organizations (government bodies, companies) providing infrastructure sign their work, and the signatures in raised or inset letters on storm grates, manhole covers, fire alarms and service boxes can last decades or centuries. At a certain point this credit-taking ceases to be promotional and begins becoming archival, historical. Steel service covers and various emblems bear the signatures of Edison Electric Illuminating, the Bell System, Cambridge Electric Lighting, McClure (a dead fiber company), MetroMedia (another dead fiber company), Simpson Brothers (a cement company laying sidewalk), and countless other names once considered permanent.
- Re-usability matters. Pipes and poles made for one thing get used and re-used for other things. Poles that first carried electricity later came to carry phone, cable TV, and fiber optic cabling to carry phone, TV and internet service.
- Ease of servicability matters. Streets are marked everywhere with red (electric), yellow (gas), green (non-potable water), orange (communications), blue (potable water) and white (planned construction) graffiti. That these are all ugly is of little concern.
- Infrastructure is vernacular. It's local, and the expertise behind it is local.
I believe it's no coincidence that we "build" code, that we have "architects" and "designers". The similarities between infrastructural software and public infrastructure are many. I'll keep exploring them. Expect a book eventually. Meanwhile, enjoy the pictures (and their captions, which comprise the essays). And share your thoughts below.
Doc Searls is Senior Editor of Linux Journal
|Happy Birthday Linux||Aug 25, 2016|
|ContainerCon Vendors Offer Flexible Solutions for Managing All Your New Micro-VMs||Aug 24, 2016|
|Updates from LinuxCon and ContainerCon, Toronto, August 2016||Aug 23, 2016|
|NVMe over Fabrics Support Coming to the Linux 4.8 Kernel||Aug 22, 2016|
|What I Wish I’d Known When I Was an Embedded Linux Newbie||Aug 18, 2016|
|Pandas||Aug 17, 2016|
- Happy Birthday Linux
- ContainerCon Vendors Offer Flexible Solutions for Managing All Your New Micro-VMs
- Updates from LinuxCon and ContainerCon, Toronto, August 2016
- What I Wish I’d Known When I Was an Embedded Linux Newbie
- New Version of GParted
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- NVMe over Fabrics Support Coming to the Linux 4.8 Kernel
- Tor 0.2.8.6 Is Released
- All about printf
- Blender for Visual Effects
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide