Recently in Matt Asay Category

Former Novell exec (and current highly esteemed blogger) Matt Asay opines on Novell's announcing that it lost the city of L.A.'s e-mail business to Google Apps:

This isn't the Novell that I know. I used to work for Novell, and have never seen the company publicly criticize a customer, not even for defection, of which Novell has seen plenty over the last decade.

It's unclear who Novell is hoping to persuade with the announcement, or what benefit it hopes to derive from it. Is it trying to stem a tide of customers dropping GroupWise for Google Mail? If so, why has it not done the same for all the companies (and there have been plenty) leaving GroupWise for Microsoft Exchange or IBM Notes/Domino?

I've used GroupWise before in a previous job. This was more than a few years ago, when a Web-based mail client as a companion to a traditional client app was a bit more novel (no pun intended, but if you choose such intention, I won't be angry about it) than it is today.

I neither liked nor hated Novell's e-mail implementation. I did find the Web component a tad awkward (but remember, this was a bit less than 10 years ago).

And today I choose to use the "traditional" Thunderbird mail client in many instances where I could use a Web-based client, mostly because the system my company uses for Web-based mail is both slow, feature-poor ... and did I say slow? A good many of my co-workers pipe their mail through Google's Gmail, and I probably should, too. If I didn't have such a favorable impression of Thunderbird, I'd probably do just that (and I could do it anyway and keep using Thunderbird if I so chose; I'm just too lazy at present to try it).

But Gmail — and Google Apps — are very, very different from the traditional way of computing, with information stored on the local drive or on a LAN, apps on the local client/drive and possibly a Web interface as an afterthought.

It's a whole new world, and there are probably more than a few companies large and small can do most everything they need with Google Apps. There's nothing stopping said companies from using OpenOffice or even the full MS Office for as many or few desktops as they wish.

And Novell never acknowledges that L.A. city workers' opinion of its services and systems is not good. Downtime is a problem.

So now it's sink/swim time for Google in the enterprise, a place where until now it did not care to tread but also where, at present, it's turning everything we know about enterprise computing upside down (along with cloud leader Amazon ... and probably soon IBM and others).

L.A.'s the big-city Guinea pig for cloud computing; in the months ahead we'll see who thinks it cute and cuddly and who smells the proverbial rat.

Someday I'll meet Matt Asay. I'm no tech executive, I appreciate but don't fawn over Macintosh laptops, but I do admire his writing at Cnet.

On Twitter's change of policy for @replies, hiding them from the unwashed Twitter masses unless the individual users are also followers of those receiving said @reply — and the furor following that change, he is a voice of sober- and business-minded reason:

For those who will chime in to voice their serious displeasure that Twitter had the gall to change a service for which these users have paid a whopping $0.00, I have two words:

Pay up.

That's right: pay money so that you actually have the right to voice your displeasure as a customer rather than as a user. Customers have a right to complain about changes of service. It's unclear to me why anyone else would.

This, perhaps, is a budding business plan for Twitter: use a free service as a grand experiment, constantly evolving and changing at Twitter's whim, with a paid service that keeps things constant for customers, and perhaps adds additional functionality or quality of service guarantees for these same customers.

Stuff like this is why I read The Open Road every day.

In other Matt Asay news: Matt claims he's far from famous:

On the Web, however, what passes for "fame" usually isn't. Would you consider me famous? I certainly wouldn't. My kids still get excited when they see my picture on my own computer...in my iPhoto application...displaying pictures I took with my own camera. Me, famous? Not even close. Not even close to close.

Never has the bar to fame been so low.

Why do I have to do anything when Matt Asay is writing all the good stuff?

I'll just do a link dump:

WSJ's Walt Mossberg: "Firefox is the best"
Google embrace OpenOffice? Probably not
Google gets serious about the Mac
WSJ to Microsoft: You need to open source Windows
The eBay "fad" is wearing off
Would we hate Microsoft if it were Apple?
The most important open-source projects...to Google
Does OpenOffice's speed even matter?
When all else fails, try porn

Matt is a big wheel at open-source company Alfresco, but he isn't afraid to write about his own company: Try doing this with proprietary software

Here he hints at his almost-working for Microsoft and former position at Novell:
Why I won't work for Microsoft:

Several years ago while still working for Novell, I considered going to work for Microsoft in Europe. (Had I waited long enough, I could have worked for Microsoft while still at Novell, but that's another story, albeit one that is paying off well for Novell.) I thought I could help the company figure out open source and navigate the thorny issues that prevent it from embracing open source.

I gave up on that quixotic quest, and in retrospect it was the right decision. Sam Ramji, Bill Hilf, and others are doing a far better job of nudging Microsoft toward open source than I would have. But the bigger reason is that Microsoft has placed an apparently insurmountable hurdle in its path to fully engaging the open-source community, and to my ability to fully support its embrace of open source:

Patents

A few more links:

The Mac's allure for open-source developers
Twitter is the Wonderbread of intellectual nutrition