The Open Road Ahead
It's a delight to debut column-wise in one of my favorite magazines, a journal that has remained finely focused since March 1994. Over the years, we've seen many computer publications falter or fade as they sought faithful readers and fickle advertisers in the face of an ever-volatile industry. There has always been a broad spectrum of editorial targets with “content-addressed” titles, ranging from the cosmic general (Wired) to the minutely specialized (printf() Daily). By “content-addressed”, I mean the magazine title aims both to capture (figuratively) the themes to be addressed and to capture (factually) a viable market segment. The old signifier-signified problem has oft raised its intractable transient-fashion semantic head.
Consider the demises of Datamation (why does this sound archaic, in spite of recent data-centric resurrections?) and BYTE (the once “in” term, with a matching chain of Byte shops, encapsulating the 1980s thrill of affordable, personal computing, but now worth a few mundane bits). Some publications have survived with brash, broad names such as Computer Weekly, a title that was quite content-specific in the 1960s but nowadays reveals only its frequency. Others have gone for “insider” titles. Thus, unless you already knew, Dr. Dobb's might at first glance appear to be yet another paternal self-health advisory. (Some Dobb's fans may say “indeed”.) Mostly, though, it's an upfront WYSIWYG world (What You Subscribe to Is What You Get). If you pay through the nose for MSDN [Microsoft Developer Network] News, that's what you'll get: the current designation, security vulnerabilities, APIs-du-jour, and ETAs for NT 5.0. (To be fair, Dr GUI does offer “work-arounds” to the baffled with non-corporate aplomb.)
There's no shortage of drop-dead titles that strutted bravely but briefly and are heard no more. I wrote evangelically, no one more, for OS/2 Magazine until it succumbed-- not for want of reader devotion (they screamed “Stan, say it isn't so...”) but for IBM's own lack of commitment and the natural ensuing reluctance of the advertisers.
Then we have the fascinating name-change phenomenon. Reacting to those restless, highly paid “demographers” who filter your blatant reader-response fibs through a statistically stunted spreadsheet, the publisher-suits are often convinced that the titular temperature needs a tweak. (Consultant Axiom #1: It's difficult, alas, for the client to ignore expensive advice.) Whether the content should change to reflect the “hotter” title is a tricky problem. Too dramatic a shift in both is rather like a new magazine launch and everything that entails. Instructive exemplars abound: Computer Language moved fairly gracefully to the less “technical” Software Development with an appropriate content-drift toward the bland. (Its “Peopleware” articles are notorious for their vacuous “Cook Until Done” recipes: “Create a well-formed plan before you start coding, and don't forget to select the best-possible team for your project...”) Similarly, following the trend set by Clemens Szyperski's Component Software—Beyond Object-Oriented Programming (Addison-Wesley/ACM Press, 1998) [Reference 1], SIGS's Object Magazine traveled “beyond” to become Component Strategies. This advance was cut short by another popular name-changing influence: the publishing trade's agglutinative propensity. Following one of those hard-to-keep-up-with takeovers (not to be confused with those equally baffling “strategic alliances”), Component Strategies has been newly “folded” into Application Development Trends. Presumably, this title allows the tracking of SE (Software Engineering) fashions beyond mere components. An interesting counter-example, where the content has been fashionably “enhanced” without a title change, is C/C++ Users Journal that now carries a regular column and even detached supplements on...shock-horror...drum-roll...Java! Recall that the earlier post-incremental title update from C Users Journal still triggers irate reader mail. Likewise, for complex “space-precludes” reasons, we've seen the long-going (1983) UNIX Review, outliving all its UNIX rivals [Reference 2], moved by market forces to (1998) UNIX Review's Performance Computing and now, as I write, to simply Performance Computing.
Meanwhile, Linux revives the old UNIX “Live Free or Die” spirit of the 1970s. The only Open Road beckons. Linux Journal leads the way. And lest we become too hyper-serious, browse http://www.gnu.org/fun/ and my next column!

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.
Sponsored by AMD
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.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- Designing Electronics with Linux
- New Products
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Linux Systems Administrator
- Using Salt Stack and Vagrant for Drupal Development
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Web & UI Developer (JavaScript & j Query)
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
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.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?




1 hour 22 min ago
1 hour 57 min ago
2 hours 55 min ago
3 hours 45 min ago
7 hours 47 min ago
11 hours 34 min ago
11 hours 42 min ago
13 hours 57 min ago
16 hours 27 min ago
1 day 2 hours ago