RCA Cables, Web Services, The Component Object Model, Boom Boxes

What if the world had never known the pleasure and convenience of RCA cables to connect disparate component audio and video together to seamlessly and transparently put together systems? It’s easy to conceptualize and implement. Application components on the other hand are still too difficult to string together for desired output in my opinion, if possible at all.

I always used the stereo system description when attempting to describe Microsoft’s Component Object Model (COM) when asked about it years ago. Similar statements can still be used in analogical ways to describe web services and Web 2.0 stuff, which seems to be back to a point where it’s again being defined and re-defined. Some people are questioning the very basis for the incremental version string applied to the “Web” monicker. I’m least concerned because ordinary people (mere mortals) can discern from the 2.0 part that “Web 2.0″ is the next iteration of what I already know but with more features. Simple. Easy. RSS — they don’t and won’t ever get that. If RSS was called Headlines — they would get that. Headline readers make sense. RSS readers sounds like a test you take at a cash for service clinic on the other side of town after meeting up with some local floozies while you’re on travel far, far away from home.

Back to components and RCA cables. Without RCA cables, we would be relegated to boom boxes that have rather monolithic designs and typically don’t support component input. When the tape drive goes bad, you’re screwed. Only a CD player and radio left, but forget ever making any mixtapes from that CD content. What’s the value in monolithic designs when distinct individual services are required to satisfy some demand? The value has and will continue to diminish as long as some smart people find ways to create user defined systems. Much is the same in the application world. Monolithic application design represents a tremendous disservice to the end user and likely the person responsible for making financial decisions regarding purchases because one will likely end up having to purchase again.

Microsoft’s COM, or any other component service oriented architecture, allows for components of an application to be stitched together dynamically to make a complete application, much like stereo components can be put together using commodity cables with very little knowledge of the inner working of the component itself. It’s a beautiful thing. And any user who is competent at putting together a component stereo system should be able to understand input/output and tweaking knobs for desired flow from one component to another. Although we’re still not quite there yet, ordinary people should be able to link disparately applications created in isolated and unique settings with applications of their own to create new functionality without the current headaches. I don’t know what it should be yet, but I am thinking about it on occassion.