Gadges and Gadgets!

Stan discusses gadgets.

It's strange how often my essential tools of trade are readily dismissed as gadgets (mandatory usage being “mere gadgets”). The doohickeys that you cherish are, of course, totally pathetic in my eyes, revealing you as a “sharper image” slave to self-defeating, fashionable mechanisms. Price and pride of ownership (closely related, nay, tightly bound) have clearly blinded you to the rational basics that guide my purchases.

The origin of “gadget” is, as the more honest lexicographers say, orig. uncertain or etym. obscure. Some guess at the French gâchette, but this was originally the safety lock-catch on a door or pistol, a reference to security and hard to reconcile with our modern “mere” gadgetry. Later, gâchette moved to become the pistol's “trigger” (as in Elle a la gâchette facile, “She's trigger happy”) which is perhaps more cognate with current gadget usage (see Note). She clicks to conquer, opening car/garage/home doors and TV channels, and, replacing old-fashioned scholarship, clicks to access the webbed windows of opportunity. Losing your clicker (I risk a gender-switch) is gadget-impotence, akin to Milton's blindness. Fear not: there's a meta-gadget you can click that will locate (beep-beep) your misplaced clicker. Lord knows what deeper levels of technology exist for recovering lost meta-gadgets. And now that mice, keyboards, modems and monitors (more) are becoming footprint-loose, wireless “remotes”, there's a growing chance of mislocation.

My own amateur spin is that “gadget” has morphologically diminutive implications (easy for me to say) that have added to its derogatory usages. I would back-form the term “gadge” to describe my own solidly justified possessions, regardless of price, conversation-party-piece, physical size and weight.

We are, patient readers, converging to a topic relevant to Linux, the OS we all love. I refer to the test known as productivity, an apparently simple econometric criterion that should (fat chance) dictate all our choices. The TV gadget heyday ads of the 1950s and '60s showed a trim USA super-efficient Mum clicking breakfast for hubby and her 2.7 adorable kids, then clicking the washing up. The general mantra “labor saving” (since applied to all forms of automation) left open the questions, “Saved at what cost?” and “time saved to do what else?” There's the ancient Time & Motion quip: Expert: “If you follow our plan, you could paint twice as many fences.” Tom, the painter: “But there aren't twice as many fences to paint.”

The equation has been obscured by the more subjective notion of “personal productivity”, yet even at the corporative level, after endlessly refined techniques and “studies at well-known West Coast Universities”, it remains dubious whether we can ever well-order our choices of computer languages, operating systems, development methodologies or guiding columnists.

Except to assert that my gadges are the best.

Note

Stan Kelly-Bootle (skb@atdial.net) has been computing on and off since his EDSAC I (Cambridge University, UK) days in the 1950s. He has commented on the unchanging DP scene in many columns (“More than the effin' Parthenon”--Meilir Page-Jones) and books, including The Computer Contradictionary (MIT Press) and UNIX Complete (Sybex). Stan writes monthly at http://www.sarcheck.com/ and http://www.unixreview.com/. Visit his home page at http://www.feniks.com/skb/.

______________________

Webcast
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions