Linked by Thom Holwerda on Thu 21st Feb 2008 21:51 UTC, submitted by Xaero_Vincent
Microsoft Microsoft rolled out its big guns, including CEO Steve Ballmer and Chief Software Architect Ray Ozzie, to underscore its commitment to the set of new interoperability principles announced Feb. 21 that are designed to increase the openness of its high-volume products and drive greater interoperability. In fact, Microsoft's long-term success depends on its ability to deliver a software and services platform that is open and flexible and provides customers and developers with choice, Ballmer said during a media teleconference. The EU is skeptical on Microsoft's pledges, according to Ars.
Thread beginning with comment 301935
To view parent comment, click here.
To read all comments associated with this story, please click here.
sukru
Member since:
2006-11-19

what about committing to open standards? hmm.. oh wait, that does not include the microsoft vendor lockin (tm)

You mean "open standards" as in LDAP, Kerberos, DNS, DHCP, HTTP, SMTP, CIFS, etc, which they use to build their server infrastructure ;)

Edited 2008-02-22 02:49 UTC

Reply Parent Score: 3

monodeldiablo Member since:
2005-07-06

Did you really include Kerberos in that list?

Methinks you need to read up a bit on Microsoft's history, specifically the bit about "embrace, extend, extinguish". Kerberos is a prime example of their refusal to play nice in the open standards sandbox.

And regarding the rest of your list: The only reason Microsoft plays nicely with those protocols is because they were asleep when the internet was exploding. Microsoft was late to the internet cakewalk, and thus was forced to play by an existing set of rules. In retrospect, this was extremely fortunate for democracy, information, and the economy.

Don't assume that, because Microsoft implements *some* open standards (and only partially, with proprietary extensions), they're doing it by choice. They're not. The world would be a very different place with them behind the wheel.

Reply Parent Score: 8

sukru Member since:
2006-11-19

Yes I did include Kerberos knowing the problems existed in the past. (And I still don't understand why I'm modded down whenever I say something positive about MS. They're not pure evil, you know?)

Anyways when necessary I was able to join an MS kerberos domain with standard Linux kerberos software (without samba tricks) very easily. MS kerberos also did set up proper DNS records for automatic server discovery.

This also occurred for LDAP directory services. I was able to access them from RedHat without any problems at all.

I'm not telling these because they're the best implementation out there. They're not. Their's is just one of the (good) ones. And don't come with (embrace-extend) accusations. They have bugs and sometimes they cannot fix it. This does not mean they want to change the protocols. (Yet in this case you just don't choose their products).

FYI: We've finally went with Fedora Directory Server for our system, even though we had Windows Server 2003 license. This came after evaluating several systems for their values.

Edited 2008-02-22 07:54 UTC

Reply Parent Score: 3

miro Member since:
2005-07-13

CIFS a standard, haha dream on, there is one old doc about CIFS and the best documentation is still samba source code (and cifs linux module). NTLM is not a standard and they force it on users even with HTTP. The problem is not that they don't endorse/use standards, the problem is that they deviate and make non-compatible extension instead of pushing for a common solution.

Reply Parent Score: 5

hobgoblin Member since:
2005-07-06

all sporting ms extensions...

Reply Parent Score: 6