Much ado about little seems to be round the latest delay that keeps Microsoft from releasing Vista, its who-in-the-market-is-waiting-for operating system. The novelty this time is about being able to glimpse at the communications (even thought process) several Vista-related constituencies have on the
Mini-MSFT blog--see the second part here.
From a customer perspective, I suppose, the impact is minimal. Why should it matter a few-month delay more than an already multi-year one? What is there that people want to capitalize on and only Vista enables them to do so? Enterprise customers will get their hands in the software this year still, yet their upgrade cycle is somehow independent of the release schedule of software providers. And, yes, the home users may get some back-to-school/holiday purchase plans redrawn, but it's not to say they'll have that much of a different alternative, financially speaking for Microsoft at least.
This delay could be more complicated for Microsoft hardware OEM partners, but even those are grown-ups with their own histories of mishaps.
More noticeable effects are likely to occur on a couple of fronts though. One is a short to medium term hit MSFT will take in the financial markets. MSFT stock has been between $22 and $28 for the most part of the last 6 years, so now it has some room to slide from $27. The other is with Microsoft's own employees who seem to be ever more confused as to what the direction of their company is. The rank and file are unhappy about the slow growth, whereas the executives have been in a state of prolonged denial. The problem with the former is their resistance to becoming more like, let us say, IBM employees; the latter seem to have run out of ideas with real impact on the markets and their own employees. Elsewhere on this blog, I even dared make a suggestion for what Microsoft might want to do--in essence a clear separation between applications/infrastructures for home and enterprise customers, respectively.
I consider Vista's delay just one more symptom, alas one of the highest visibility, of the problems companies in general and Microsoft in particular face. This is to say nothing about the novelty Microsoft has been trying to pull off: to have a major redoing of a multi-million line of code piece of software every few years...
Per chance you have not visited
Mini-MSFT lately, here are my favorite three comments about the market delay of Vista:
First, calling it an operating system is a misnomer. It is a bloated 'user experience' that has no relationship to an operating system.
Second, XP ('ancient' 'years old') is the first stable general market OS you folks have produced. Yes, NT was a decent product and 2000 was fine and started the transition to the general market but XP is still good enough based on your history. And I have no incentive to rush to Vista.
You produce bloatware. And all indications are that the Vista bloat will follow Moore's law once again.
You aren't producing operating systems you are following a business plan. And you do that very well in a totally selfish and proprietary manner that has had its obvious success.
But, I really wish you'd quit calling yourself something you aren't.
I have used 2 stable OS's in my long life--CP/M on the 88 series and OS/2 w. 386. And I have used a reasonably stable x86 product with XP.
I guess you might call me a MS basher but I am also a realist. I have no incentive to be a masochist and run an alternative OS. But, the cost is all the crap MS makes me use a better processor and more memory than my 'real' applications require.
I run the applications that I want to use and they are on the MS platform. But I can live without the 'enhanced user experience' that you are selling. As a long time (retired) consultant and programmer to industry, I'd have no qualm in telling any former client to wait and wait whether Vista shipped tomorrow or in the next decade.
You are very accurate in one area--you folks are really full of yourselves.
I think this is all a huge laugh. I recall Bill's comments back in DOS days about a bloated, decisionless IBM that he was out to take down. He should have read Pogo rather than computer journals--we have met the enemy and he is us.
KenP
I'm just a simple sysadmin that has to install and maintain Windows but I agree that the direction the OS has taken with Vista/Longhorn is several steps backward. It appears that MS is losing sight of exactly what Windows is used for.
Basically it's just a tool; for business and for entertainment. Adding eye-candy doesn't improve the mix; it makes it more difficult to support and more expensive to re-train.
Yes, MS needs to correct the Windows team problem, but it also needs to reconnect with the users.
If anyone needs to see some good examples of what NOT to do with a good OS, slide over to the V/LH beta newsgroups and read what's being posted. It's quite an eye-opener.
Mark-Allen
And now, the third, which reminds me an entry into the
Ideas Lab section of this blog, about
Agile software development:
It dawned on me during the commute over the 520 bridge: I'm irritated with all the recent sh*t-flinging at the company, but I don't think Vista inherently sucks. I think it is just too ambitious a project. Just like WTT (WDK for external folks) What a piece of garbage WTT continues to be. I can't even get my daily stress runs to count in the stats pages lol!
Anyway, these big projects look great on paper, but when it comes time to implement, it quickly becomes a crap-fest due to the complexity. As a low level employee, I can't even fathom how you could possibly manage all this properly. Is there a comparable software project out there of this complexity? I doubt there is anything that matches the lines of code...
I think Windows should trim down the release cycle and become more like NASA. Instead of flying men to the moon, just do smaller, manageable projects here and there. A probe one year, a rover the next. Makes the news; gets the budget dollars flowing; keeps people excited.
We can do this with Windows. We did some awesome stuff with XP SP2. OCA hits went down big time. Games started working again. Data execution prevention opt-in improved security. Ok not the most glamourous examples, but I hope you get the idea: we made stuff really work.
Why not have Windows be a real subscription service? In order to download the next new feature, you have to subscribe and activate your copy. Don't want Windows Parental controls? Don't subscribe. Don't want Media player eleventeen? Don't subscribe... Don't want LDDM/avalon/glass? Don't subscribe.
Anonymous
In the third comment, I think the anonymous Microsoft employee is onto something. Except that the process s/he is describing cannot be applied to all product lines at her/his company. And I would contrast the process advocated by this employee with the observation KenP made about what appears to be (driving) the current process:
You aren't producing operating systems you are following a business plan. And this is only to show how far the far-between is.