The easiest way to fix performance (if it's really an issue) is to run Apache on FreeBSD.
The most direct way to fix Microsoft, if it attempts to create proprietary client-side hooks for MS server features, is to boycott such sites and make noise about it.
I don't think Microsoft will be able to transcend the breach between servers and clients.
There will always be those who know better, even if only dimly, and "everyone else" = mass market = 'stupid' public. All Mr. Jones needs to know about his 2000-based 'server' (if he gets that far) is that half the world can't view it; he'll ask his nephew, his nephew will explain the difference between Microsoft software and the rest of the known universe, and Mr. Jones will be convinced to abandon his toy in favor of something real (Apache, which will run on 2000 and still be free) and that's all she wrote.
unification of Unix
I'm glad to see the momentum behind Linux, because Microsoft needs to be destroyed (freeing hundreds of programmers to do more useful things.)
There may be only one NT, but if it sucks, who cares?
My prediction is that by the time Linux obviously has the momentum to overtake Microsoft, BSD will be the system of choice among those in the know - say by about 2004/2005. The merger of BSDI and Walnut Creek provides a better base to try to unify the BSDs, and through that process developers should look forward to an integration of Linux and FreeBSD (Linux warm-and-fuzzy forward, FreeBSD kernel.) I'm not holding my breath for that, but I do look forward to a unification of standards.
And as always, looking forward to never having to support another Windoze machine whose OS is provided by a company that can't spell 'management', 'methodology' or 'modular'.