Horrific blog by an ex Microsoftie on possible reasons for Vista’s slippages. Comments such as An architectural diagram of Windows would suggest there are more than 50 dependency layers (never mind that there also exist circular dependencies) are enough to set any software developer’s hair on fire.
But the silver lining is that if Microsoft by some amazing effort does manage to deliver Vista after the current death march, it is only because they were one wafer short of too much. Which does not make Vista just right like Goldilocks’ third bear; it makes it just wrong. The silver lining is that MS will have reached the end of the road for monolithic systems, and will have to re-architect for the OS after Vista.
But if Vista is so complex that it cannot have a future, why would anyone adopt it? Is that really what all the Windows Live stuff is about, having a good Plan B in place in case Plan A implodes?
The blog also contains a curious bit of logic. The blogger estimate programmer productivity at about 1000 new lines of code per year, compared to 6250 lines average in the US currently, down from 9000 in the recent past. He says So Windows is in bad shape –but only by a constant, not by an order of magnitude. But what if it is an order of magnitude and a constant? If you catch my drift.
Or is this all a terribly clever development strategy to explore the limits of monolithic development: announce an impossible set of features then backpedal until something can be delivered! Embrace that the reality will fall short of the vision. The Jenny Craig school of software engineering, serving only pasta.