As to situations like what you describe with file sharing in a certain environment that mostly comes down to insufficient beta testing and straight up prioritization/de-prioritization of certain issues.
I don't think Microsoft realizes how enormously performance contributes to user dissatisfaction with their OS.
As a web developer, I know that adding just a second to a page load massively diminishes perceived usefulness of a system; Google spends enormous amounts shaving tens of milliseconds off their page displays.
At the level of an operating system, that kind of user sensitivity to performance must be at least the same if not magnified. It seems like performance, especially on older hardware, should be far more of a priority for Microsoft than it apparently is.
My experience and observation is that performance improvements of substantial magnitude are often available for the taking in almost all software projects, but it requires a concerted effort to realize those improvements. MS instead spends its efforts on merely making sure that the software doesn't get slower by too much.
I installed Windows 7 on 2 laptops of family members. These laptops were $300 from Walmart. Windows 7 runs just fine.
I installed Windows 7 on an Asus EEE pc. Runs about as well as Windows XP (only computer where I can tell it runs a littler slower).
Considering a ~$800 ipad that isn't a full computer...
I fail to grasp what kind of performance you expect to get out of Windows 7, while at the same time having a full featured OS at the same time running on _affordable_ hardware.
It is called the "Redmond reality distortion field"
So a company like Microsoft can invest in the 80% of the market that drives sales (ie. people who refresh computers) OR invest resources in solving problems for the 20% of people running old hardware with an old OS they bought a long time ago.
Should the state of the art be driven by the fact that your employer chooses to leave you with a laptop that cannot play YouTube video?
Even accounting for business clients on hiring binges, I'm really, really certain that the vast majority of the PCs that we support are more than 4 years old.
But my perspective is that I would probably prefer not to have those particular lemons! My time is valuable to me, and so is my patience. And as a software developer, I spend far more time using other peoples software (IDE, DB clients, etc) than I do using my own.
The best way I can better my products, I think, is to devote as much time as possible to fixing bugs and adding features. Time spent waiting for my IDE to load is time spent not adding value.
I, personally, am far less inclined now to spend my coding time on new features, and more likely to spend it on refining what I already have -- and so far I've gotten really positive feedback from customers on that.
The ideal situation would be a blazingly fast machine for compiling, linking, and running automated tests ... and commodity hardware for day-to-day tasks including browsing, email, word processing, spreadsheeting.
If that's true, do you think the software developers have done a good job?
And if that's not true, then why shouldn't they use commodity hardware?
I own a small company that handles a lot of end-users' various issues. Although I spend most of my time now coding, I spent more than my fair share of time working one-on-one with individuals and companies that were having problems with their systems. I still spend around 10 hours a week doing it.
My primary development machine is an aging laptop that can't even play YouTube videos any more without stuttering. I hate almost every minute of using it. It's slow, and limited, and it hangs.
So when I write something, I write it to work well on that laptop, because I know there are lots -- lots -- of people out there with similar old hardware, and to say they're frustrated with computers is an understatement.
How could a Windows developer possibly understand just how frustrating their product is when they spend all of their time using the most powerful hardware available?
How could they possibly understand that Windows file sharing in a mixed environment running SBS 2008 is still complete and miserable and utter garbage, when they're running on a network that hides those kinds of issues?
Their development process is great for their developers. No argument there, and I'm totally and unabashedly envious.
It's also terrible and completely wrong for most of their many users.