In what would rank as probably the shortest Larry the Free Software Guy blog item in the history of, well, Larry the Free Software Guy (and the blog’s predecessor, Larry the Open Source Guy), here’s a classic Mark Terranova mash-up of Red Hat’s Karsten Wade — Obi-Wade Kenobi — and Larry the Free Jedi Guy.
May the fourth — I mean, force — reamin strong with you always.
This blog, and all other blogs by Larry the Free Software Guy, Larry the CrunchBang Guy and Larry Cafiero, are licensed under the Creative Commons Attribution-NonCommercial-NoDerivs CC BY-NC-ND license. In short, this license allows others to download this work and share it with others as long as they credit me as the author, but others can’t change it in any way or use it commercially.
(Larry Cafiero is one of the founders of the Lindependence Project and develops business software at Redwood Digital Research, a consultancy that provides FOSS solutions in the small business and home office environment.)
This week there was a sort of back-and-forth starting with Brian Proffitt in one blog item about Richard Stallman’s somewhat verbose Guardian article and a response by Bruce Byfield in a blog item about how he notices that lately people are picking on the Free Software Foundation. This kind of tete-a-tete is normally custom made for my participation, and last night I had thought about jumping in with both feet and an arm.
But you know what? Never mind. Just never mind. I had a whole blog item written last night. I went to bed. I woke up this morning and read my item. Then I deleted it. It’s just another “fuel, meet fire” situation that, despite my standard-issue remarkable and compelling prose (ahem), would have just removed focus from more important issues and would have created ill feelings.
So I’m just going to shrug, say “Ho-kay,” and write about something else.
Before I do, however, I will say that I do think Brian is right when he says that the Guardian article is another FSF broadside against open source, and that I don’t agree with Bruce’s arguments that the FSF is being picked on. Let’s look more importantly at the latter: The FSF does a lot of great things on behalf of software freedom, and does so with remarkably few resources. For this we are truly thankful. On the other hand, the FSF tragically has made an exact science of cultivating a “my way or highway” attitude (bring up dissenting viewpoints, as I have, and see how far you go), which makes its prevalent dogmatic stance a formula for organizational rigor mortis. For this reason alone (though there are others I won’t go into here), the FSF hand-delivers invitations for criticism — some of it deserved, some not — rather than than being victims of attacks for whatever reason externally. For all the great things he has done, Richard Stallman is largely responsible for this culture of dogma and rigidity, and when some — not me, but others — equate the FSF to being the FOSS equivalent of the Taliban, I’d like to argue against that comparison but, honestly, I really can’t.
But never mind.
Let’s go from one train wreck to another, shall we?
One of the items that is high on the tech radar today is the fact that Hewlett-Packard is about to push Leo Apotheker off the top of the building (the sentiments of some board members, it’s safe to say) and replace him with — I kid you not — Meg Whitman.
Meg Whitman. I would have prefered Slim Whitman — link to Wikipedia provided so the kids here don’t have to Google him. So while you read who he is, get off of my lawn.
This Whitman-for-Apotheker swap has been described as a “hangover solution” in one ZDNet blog item, a sort of “hair of the dog” after an all-night bender where the first question is, “I did . . . WHAT?!” And the best decisions are usually not made when you’re hung over. Hence we have Meg Whitman waiting in the wings when, according to people at HP, they have a very capable CEO choice in house with Ann Livermore.
While it would probably be best for HP to keep someone in house at the helm — that’s one vote for you, Ann, over Meg — whomever takes over hopefully will say, with one of their first utterances in charge, “Remember what we said about dumping our hardware and WebOS? We take that back.”
That would be nice, but on the whole that, too, probably deserves another shrug.
OK, it’s crunch time. At the end of the week, you should be in Columbus, Ohio, at Ohio Linux Fest –if you’re going to a Linux show before the year’s out, make it this one. This is the last big show on the North American continent until SCALE in January. At OLF, Bradley Kuhn and Cathy Malmrose are keynoting — along with Jon “maddog” Hall — so you’ll not want to miss that (especially Cathy — Go ZaReason!).
Many of you already know this, but for those of you who don’t, I don’t do tech for a living. I’d like to it for a living, and I’m working on that. This is why you’ll find me with my nose in a book, studying for the Red Hat Certified Engineer certification test I’ll take someday (and, if I ever scrape up enough money, Red Hat classes).
What pays the bills — what I’ve done since my first day on the job at The Miami Herald on President Carter’s inauguration day (yes, I’m that old, and get off my lawn) — is newspaper work. I currently work as a copy desk editor at the Santa Cruz Sentinel, but it’s a news career that has spanned three decades, three different media (print, TV and radio) and two continents.
I am a third-generation man of letters: My father was also a newsman and his father was a mailman.
I bring this up because at the Sentinel I am known as the Grammar Hammer; a moniker which I am honored to have and one that I constantly strive to live up to. I have a three-pound sledge at my desk. I wield it with the same conviction and passion that Thor might wield his hammer, only instead of vanquishing bad Nordic guys, I’m vanquishing bad grammar and spelling.
As you might imagine, I spend a lot of time reading; more than I spend writing, as a matter of fact (isn’t that always the case?). In much of the tech realm — most in forums and comment sections — the spelling and grammar aren’t always what they should be for people who, generally speaking, are smarter than the average person (and sometimes are smarter than the things they say. But I digress . . .). In the grand scheme of things, that’s OK — I’m not really that interested in picking nits, gramatically speaking, as much as I am concerned with content.
[Note to those who speak English as a second-, third- or fourth-language. This does not apply to you, and thanks for making the huge effort to communicate in tech's lingua franca. My hat is off to you, and thank your lucky stars you don't have to communicate with me in Spanish or Japanese, the only other two languages in which I can communicate. I dare not say I "speak" them.]
But there are a few things that drive me up the wall and across the ceiling when it comes to grammatical and spelling morsels I see in comments and forums (and even in tech stories and blogs, albeit rarely), like:
MAC, as in Macintosh: It’s not an acronym. Mac is short for Macintosh, the product from the new evil empire based in Cupertino called Apple. It’s big-M small-a small-c. Not to be confused with MAC, as in MAC address, which is the Media Access Control address, and the MAC there should be all upper case. The next person who writes MAC to refer to the Macintosh, I’m going to come through your screen with hammer blazing.
It’s Xfce, but LXDE: With all the desktop hubbub going on, these two up-and-coming environments sometimes get mislabled. I’ve seen it XFCE and Lxde, most recently in discussions on the Felton Linux Users Group, which is going great guns in the desktop debate on the mailing list. I’ve never understood why Xfce is 75 percent lower case, but it is. LXDE, according to its site, is all upper case. Speaking of all upper case . . .
GNOME, not Gnome: This is not a GNOME 3 issue, surprisingly. A general rule of thumb is that if it’s an acronym, it’s all upper case. GNOME originally stood for GNU Network Object Model Environment, though I understand that this was so long ago in a galaxy far, far away that some want to drop the caps. I can live with “Gnome,” but on a purely grammatical stanpoint, I’ll keep capitalizing it, thank you. Besides, GNOME folks, do you really want KDE to be the only major desktop environment to be all caps? Fuel, meet fire . . . .
There are more, of course, otherwise I wouldn’t be the Linux curmudgeon that you all know and love; at least the Linux curmudgeon you all know. But you get the idea.
All of which is to say, when posting here or elsewhere, let’s be careful out there. Dot each i. Cross each t. Don’t dangle your participles.
This blog, and all other blogs by Larry the Free Software Guy and Larry Cafiero, are licensed under the Creative Commons Attribution-NonCommercial-NoDerivs CC BY-NC-ND license. In short, this license allows others to download this work and share it with others as long as they credit me as the author, but others can’t change it in any way or use it commercially.