The kerfuffle this morning on TechMeme is mostly over a purportedly leaked memo from Microsoft's Sales, Marketing, Services, IT, & Operations Group banning iPad and Mac purchases by employees.
There are a predictable range of responses to this so far. Some folks point out that, considering that this group includes sales teams that are supposed to be out there pitching Microsoft products, it only makes sense that you wouldn't want them to be seen personally using competing products. That's pretty simplistic; the group also includes a lot of folks who aren't out selling directly, and even among those who are, Microsoft still makes plenty of software that runs on Macs.
Considering both that and the fact noted in the memo that there are apparently relatively few of these purchases already, you have to wonder why they bothered putting out a memo about it in the first place. Bureaucratic caprice? Petty string-pulling? Because it was almost sure to leak, and the impression it was sure to give was that Microsoft products are so crappy compared to Apple that the company can't even get its own employees to use them without banning the competition.
I don't believe that is true; there's not a huge epidemic of Mac adoption amongst Microsoft employees that I have seen. The company could have easily ignored what little of this there is and focused on combating that with more aggressive employee discounts or flat-out itch-scratching feature delivery.
Instead, they sound threatened, which only makes Apple look more formidable.
Before you run away screaming, don't worry: let me assure you I do not plan to offer yet another definition of "cloud computing" to join all those hundreds of other divergent definitions running around out there.
They both cite the current NIST definition of the term:
“Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.”
Which is not the worst definition I have heard today. But then both Dave and Joe argue that it doesn't go far enough. I'm not sure how Dave squares that with his earlier assertion that "extensive overuse and misuse" have rendered the phrase nearly meaningless... it seems to me that "overuse and misuse" are just a result of other folks broadening the definition in ways that he does not approve. He goes on to say:
The concept of cloud computing is about the ability for organizations to stop solving all IT problems by themselves. It's certainly about sharing resources, such as storage and compute services, but it really should be more about sharing solutions and pushing risk out of the business.
Really? Outsourcing is now also "cloud computing?"
I tend to agree with Joe when he says "Ultimately, the term may disappear, vendors will move on to hyping the next big thing, and we’ll remove the “cloud” from “cloud computing” as it simply becomes a ubiquitous method by which applications and services are assembled and accessed." The hype, however, is coming as much from these columnists as vendors, and all seem equally culpable in my view of distorting and diluting the term.
Which is why I will continue to avoid using it inasmuch as is possible.
Like everyone else, I was reading over James Whittaker's blog entry this morning on why he left Google to return to Microsoft. The post comes off a little whiny, but that's the nature of these things; when you feel a little betrayed about something you once believed in, you tend to glorify that storied past and bemoan the benighted present. I've cranked out a few of those myself.
Whittaker points to the surge initiated by Larry Page to compete with Facebook as the source of these ills, and to Google+ as an example of all that is now wrong with the company. That's not the first place I've seen this argument in the past few weeks. Paul Graham makes a similar point, tangentially, in his list of ten ambitious startup ideas. One of those ideas is "start a new search engine." Google, having taken its eye of the search ball and become embroiled in its pointless losing fight with Facebook, is vulnerable in what once was its core strength. And even as the company has narrowed its portfolio to focus on social, I was reminded of how the few remaining product lines still receive short shrift as I look over complaints about Apps, or the horrible changes that have been jammed down onto Gmail and Reader in purported service of this larger social good.
Google has always been two different businesses (in the sense that they actually function as a business; this doesn't include their various digressions and experimentations, even the most popular of which have never had broad adoption or generated significant revenue): internally, as Whittaker points out, they are an ad company, and an extremely successful one; externally, to their users, they are a search company, and they had been extremely successful at that until recently as well. Whittaker attributed this to "good content" but the content isn't, and never has been, Google's... it is generated by the rest of us and Google's particular and appealing genius was to index it and make it accessible, while throwing some unobtrusive ads up alongside it to support the whole experience.
The company has long attempted to break out of the search box in the minds of users, looking for something more sticky and valuable to serve them with, but has made a poor job of it at every turn. What is happening with the Google+ social push is even worse, however. In desperately attempting to shoehorn existing properties into the big Google+ family, the company has diminished, rather than enhanced, their value to users. I can no long frequently recommend Apps as a solution for businesses, for example, because the company is not only divorced from core Apps services as a revenue stream (this was always true and always a moderate risk), but is now visibly desperate to somehow make everything "social" at the expense of core functionality. The "Search Plus Your World" tinkering with search is a frightening and potentially damaging example that could mark the beginning of a steady deterioration in the very business that users turn to the company for.
Graham compares Google's obsession with Facebook over Microsoft's with Google and I think that's apt in most respects. Microsoft saw Google's philosophy of computing services as a threat and made the mistake of thinking that Google itself was the threat, and attempted to mimic them to compete, making a poor job of it. Google seems to be taking the same tack with Facebook. This isn't necessarily to condemn either Microsoft or Google; the philosophies they are up against are existential threats to their existing businesses, and it's always a tough call to find a way to reinvent your business without cannibalizing it. Microsoft, despite several mis-steps, may in fact be doing a better job of this than Google is. One can only hope Google will similarly find a workable solution to their own dilemma.
Unlike Microsoft, however, Google doesn't have the advantage of a massively entrenched product infrastructure that would take decades to supplant. Moving ad dollars and searching eyeballs to a competitor is the work of minutes. If their moves have a whiff of desperation, it's desperation well-earned.
Sixty Minutes ran a segment on Stuxnet and cyberwarfare in general recently (here's the clip, courtesy of ZDNet). There's nothing in the report that doesn't reflect information that hasn't previously been published elsewhere on the Internet, but they do interview some of the key players in tracking it, and a number of other experts discussing the potential impact of similar efforts with other targets. These represent the usual gamut of fear-mongering conspiracy theorists with extravagant, devastating scenarios.
I don't want to lend substance to the more dramatic predictions but I do want to point out that the acceptance that computer attacks will be an increasing component in state and non-state conflict is gradually entering the mainstream. There are real and expensive and potentially dangerous outcomes that can be associated with such attacks, certainly. But the point the piece makes that I want to reinforce is that the consequences, whatever they may be, are not going to primarily be faced by government professionals or the military. They're going to be faced by businesses and individuals.
Critical infrastructure for the Internet isn't run by the government. It's run by businesses. The techniques for attacking it are, today, frighteningly distributed, primarily across domestic computers run by private businesses and citizens. Although botnets may be controlled by malicious actors outside our borders, the actually machinery and code that will be involved is our own. In a hideous betrayal, our own poorly secured systems are likely to come to life and betray us. And this is not a danger that the military or some faceless government agent can protect against. This is a responsibility that rests on the shoulders of businesses large and small. That's not a patriotic call to arms, it's simply the reality of this sort of conflict. And right now, most of us are very poorly prepared to deal with that reality.
So the next time you think security is someone else's problem, that no one cares about your PC or your small business, consider the larger forces at work out there, and go upgrade your anti-virus!
If you're like me, you've already seen this, and you really don't care. Normally I agree with Joe Wilcox but I think he's dramatically off-base when he calls it "a disaster." The new logo unveiled last week by Microsoft for their core Windows franchise is almost utterly irrelevant to the product and brand impression among its core customer base: geeks.
I'm not saying that geeks don't get brands, we do; it's just that "branding" is not about visuals and color schemes and such, but about functionality and capabilities and other practical matters. There's no doubt that Windows has a brand image in the IT world. It just has nothing to do with what has always been a pretty lame logo.
Neither am I saying that geeks are the only people that run Windows... quite the contrary, in fact. Geeks tend to run more sexy and robust operating systems. But geeks are the ones who generally decide, in some way, shape, or form, what everyone else ends up buying for their day to day use. Whether it's the geeky IT manager who sticks with Windows because it's the safe choice at work or the geeky teen who would love if his parents ran Linux but knows that Windows is the best possible compromise for them, geeks drive Windows adoption. And geeks, among their many other fine and noteworthy qualities, just aren't noted for their taste and style perception. I mean, really. You've seen how we dress, right?