Microsoft fesses up
The gist of it is simple: in
2004 Microsoft came face to face with what I and lots of other
folks suspected about Longhorn: it was a plate of ugly spaghetti that
was never going to work. Microsoft sucked in its gut and threw the whole thing out, starting over from scratch. Finally we know the reasons behind the
mysterious sliding release dates: it all went in the dumpster and they had to start
Microsoft says that the new Vista is clean and simple from the ground
up. But there's a telling quote in there from Chairman Gates, who said:
It's obviously my role to ask people, 'Hey, let's not throw
things out we shouldn't throw out. Let's keep things in
that we can keep in.'
Yeah. Pour a healthy dose of the same old polluted water into fresh
new drinking glasses and what do you get? Why, it's the "Windows Experience"
all over again, isn't it? Well, only time will tell what this beast
really looks like after all the crap they can't live without gets
bolted back on, but my bet is that they'll be broken again before
they get it out the door.
Here's another interesting quote from the article:
Mr. Allchin's reforms address a problem dating to Microsoft's
beginnings. Old-school computer science called for methodical coding
practices to ensure that the large computers used by banks,
governments and scientists wouldn't break. But as personal computers
took off in the 1980s, companies like Microsoft didn't have time
for that. PC users wanted cool and useful features quickly. They
tolerated -- or didn't notice -- the bugs riddling the software.
Problems could always be patched over. With each patch and enhancement,
it became harder to strap new features onto the software since new
code could affect everything else in unpredictable ways.
Hello Bill? What's changed? You still don't have the time,
so you'll still be adding new bugs in your fever to get new features
to users. Maybe Allchin managed to deliver a clean start, but your
programmers will muck it up immediately.
Make sure to send your Windows buddies a link to this. They won't
want to read it, but I think it might be good for them.
If this page was useful to you, please help others find it:
More Articles by Tony Lawrence
- Find me on Google+
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site:
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Publishing your articles here
Jump to Comments
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
I am a Kerio reseller. Articles here related to Kerio products reflect my honest opinion, but I do have an obvious interest in selling those products also.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.