Perl, I say!

At last week’s Philadelphia Perl Mongers meeting, I asked what’s new and exciting in Perl since I last used it exclusively, circa Perl 5.6.  Walt chimed in with say, a command that prints an expression and adds a new line at the end.  New and exciting?

Other languages have always had separate commands to display strings with or without newlines at the end.  Embedding escape codes like \n or using Perl’s smarts around concatenating and contextualizing work fine, so a separate command isn’t necessary like in some of those other languages with print and println or write and writeln.  ”So why now?” I asked.

Some of the semi-glib responses to my follow-up touched on the venerated trait of laziness among Perl programmers and joking about doing more with less (i.e., two less characters from print to say). I say semi-glib because both of these comments hold kernels of truth about Perl that originally drew me to the language and explain my continued frustration with the “newer” languages that I now have to call bread and butter.

Perl has always been a programming language for the lazy, proud, and impatient.  From personal experience, I’m more likely to use print with a “\n” than without, so that little extra work spread out over the thousands and thousands of print “…” does add up. There is some sense in having a command whose default mode includes a linefeed.

Perl has also always been a language about packing–functionally and semantically. That’s earned it a reputation of being hackish or too clever for itself, but anything taken to an extreme can be bad.  My experience supports the perlish idea that less code written is less code to debug or relearn later.  Some languages, especially those fond of methods on literal strings instead of operators, provide flexibility at the cost of verbosity and ugliness.  The idea of packing more capability into two less characters is very, very Perl.

There’s talk of trying to reinvigorate the Perl base and recover some of the mindshare (and subsequent marketshare) that Perl’s lost over the last decade.  I don’t think say will convince legions of .Net or Java programmers to switch, but I’ll definitely use it my next script.

From the Perldocs on say:

  • say FILEHANDLE LIST
  • say LIST
  • say

Just like print, but implicitly appends a newline. say LIST is simply an abbreviation for { local $\ ="\n"; print LIST } .

This keyword is available only when the “say” feature is enabled: see feature.

Posted in Journal | Leave a comment

Beating a Dead dmHorse

Puppies!

Don't google "dead horse" for images.

My response to Pie’s Quality of Documentum Over the Years bears repeating, even if I am beating a dead dmHorse:

I started with version 2, back when I was just a newly-minted UNIX geek. One thing you missed with the transition to 4i was the introduction of the DFC. DMCL had a very UNIX feel; a simple, open API designed to be glued into any programming language. DFC was just Java then, with a COM layer growing over it later. That was also the point where EMC became more marketing-driven and started chasing the Internet bubble at the expense of their existing clients.

Both were attempts to capitalize on hot topics of the time, Java and the Web. I never bought that the DFC would make a whole pool of talent available; Documentum’s about the model, not the means. However, the marketroids successfully reframed it. Hiring managers now believe they can take Java people and mold them into Documentum people, and I hear gasps of disbelief when I say Java or Visual Studio aren’t requirements to do Documentum–a good Java programmer is not necessarily a good Documentum developer.

This Java mentality did increase the number of people with Documentum on their resumes, but the talent didn’t increase as much as the volume. It just diluted (maybe also tainted) the pool. It became harder to find good people in the now-mirky waters.

The lack of focus then is what brings us to the lack of quality now. Innovation at the model and server level is rare, and frankly I don’t give Documentum much geek cred anymore because of it. Great ideas like BOF and Aspects are stapled into an API rather than made an inherent part of the product. Too much work up the stack (and on vertical solutions) has made the product top-heavy and tottery. EMC continues to chase markets (i.e., case management) rather than concentrate on making a solid core product.

Posted in Articles | Tagged , , , , , , | Leave a comment

Documentum & The Private Option

I want a private equity fund to buy Documentum from EMC and give it a real shot at regaining its former glory.

#26698 Smart Cow Playing Dead To Avoid Going To The Butcher Shop Clipart by DJArtNoted rumor-monger  Brilliant Leap speculates about Documentum in a world without EMC. Tongues were already wagging at EMC World about the SAP-EMC partnership leading to something a little more intimate. It has enough of the smell of truth to make an irresistible rumor.

As rumors go, I still prefer the Microsoft angle because of the obscene anatomy kissing that IIG is still doing.  Truth is it’s just to easy to dispel: Why buy the cow when you get the milk for free? I doubt Microsoft will be stamping shrink-wrapped boxes of SharePoint with Documentum Inside! anytime soon, but I’d bet they have an infinite number of code monkeys banging away to make their own document management Hamlet. Once they do, it’s bye-bye Documentum! Then all those monkeys will get down to business and start flinging feces IIG’s way.

Part of Documentum’s doom was being a software company bought by a hardware company; however, it won’t be saved if another software company buys it next. Such companies (SAP included) would buy Documentum to augment their flagship product, not eclipse it.  With no Fairy Godmother rescue from being passed around from one wicked step-mother to the next, this story’s ending will be more Le Boheme than Cinderella. Or worse, a more-jackal-than-wolf company that hasn’t innovated for decades might gobble it up to suck the last trickle of marrow from its cracked bones.  *cough* computer associates *cough*

I am no Wall Street cheerleader, especially after my time in Big Finance, but the closest thing to a Fairy Godmother out there is a technology-oriented private equity fund. Such a fund buys troubled companies to turn them around and sell them for a profit. Unlike most of Wall Street, they take the long view of years rather than a quarter or the milliseconds around a stock’s uptick.

Their methods can be harsh, but their goal unlike any step-mother’s would be to make Documentum the best product and most profitable (and saleable) brand it can be.  There may still be an ounce of brand left to save. By going private, the recuperating Documentum wouldn’t be burdened with public company regulation or the tyranny of speculative stockholders. It’s an imperfect cure for the age of gratuitous IPOs and acquisitions fueled more by irrational exuberance than smart business.

We have a test case with AOL selling Bebo to Criterion Capital Partners, LLC instead of just shutting it down. Taking Valdes’s animal shelter metaphor a little further, I’m sure Criterion will euthanize Bebo and reap their own “meaningful tax deduction” if the old dog can’t learn new tricks. Sometimes I think I’d rather see that happen to Documentum than sit through the EMC’s little opera until the consumption takes it.

Posted in Articles | Tagged , , , , | Leave a comment