Seven Reasons Microsoft Loves Open Source

tlockney writes "Next week at Microsoft's MIX, whurley will be leading a discussion on 'Open Source, the Web, Interoperability, and Microsoft'. To kick off a bit of pre-session discussion and enlist the help of others in putting Microsoft on the spot, whurley, king of all things open source at BMC has written an article entitled 'Seven Reasons Microsoft Loves Open Source'."

Comments

Re:Reason zero

[truthsearch]

In 2003 Microsoft listed Open Source in their SEC filings as a threat to their business model. Before then they mostly ignored it. Then it was "a cancer." And now they pretend to like open source. I hardly consider them "on the wagon" as much as realizing they must augment some of their practices in order to compete affectively.

Re:I can see microsoft doing what apple did

[DECS]

You are uninformed.

Apple not only maintained is own Unix distro of A/UX, sold AIX servers, and created its own Linux distro prior to OS/X, but also ported the Mac environment to other Unix variants, using MAE and laster MAS.

- Steve Jobs and 20 Years of Apple Servers

And everybody knows that NT's "POSIX compliance" was a bullshit dance designed to make NT legal to sell to the government. NT never offered anything more than pretend support for POSIX, and it was of no more importance to Microsoft as a subsystem within NT than was OS/2.

Further, since POSIX compatilbility is techniclly a paid seal of approval on a specific implementation of Unix APIs, of course Linux as general idea can't ever techically pay to attach the POSIX trademark to itself in the way Microsoft pretended to.

The reality is that the only value of POSIX is as a general synonym for "Unix-like compatibility." In the real world, Linux currently helps define what that is; NT does not offer this at all.

Are you really trying to argue that NT provides some useful sort of compatibility for Unix apps? Citing the Wikipedia as a source does not do much to create credibility for your conjecture.

NT POSIX memories.

[EmbeddedJanitor]

As the parent says the NT POSIX was severely sucky.

In the NT3 timeframe (approx 12 years ago now), there was a big effort to sell NT to companies, such as the one I worked for then, supplying back office /server room style products. Many/most products of the time were running on Unix boxes or similar. We were using Unix x86 boxes (SCO etc) for compter tephony applications. NT had to check a few boxes to encourage people to switch: POSIX and streams driver support. This gave people a reasonable porting avenue to a cheaper OS (NT was about half or a third of SCO's cost at the time).

The POSIX and streams drivers were very inefficient, and were dropped within a short while (once the bait and switch had worked).

This ploy was very clever on MS's part. Using ourselves as a benchmark for people in this space, our customers were putting on some pressure to provide NT based products because they were eating the MS blurb and wanted to reduce costs. Our techies looked at NT and figured out what would be needed to port: POSIX-check, streams driver model - check. So we say that on paper it can be done with trivial architectural change. Marketing start hyping the NT-based offering. The business people say make it so, so we do. Unfortunately we find the POSIX and streams driver model are very slow on NT, so end up having to start doing native drivers and non-POSIX code. We start slipping, marketing starts screaming and the portability gets dumped in favour of getting shipping. The bait and switch has worked.

We never got any benefit from NT POSIX or the MS streams driver. Our systems went from requiring low-end (16-25MHz) 386s to 100+MHz 486. Basically a very bad case of bait and switch.