Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

> pick an internet or engineering standard: implement the standard in a correct, technical way (Embrace); add MSFT proprietary extensions using an IDE, a method of notification, graphical desktop software with convenience functions, etc (Extend);

You're sort of glossing over how this works in practice.

The extensions to the open standard generally cause interoperability to be one way: the Microsoft implementation can interoperate freely with the open implementation(s), but the reverse isn't necessarily true (or if true at the outset, isn't guaranteed to remain so). There is often also a way to use or operate the MS implementation in a fully compatible mode, but it isn't the default configuration (and an update will often revert to the default), and requires forgoing the functionality that the extensions provide.

There is a bit of "boiling the frog" aspect to this, with incompatibilities (usually experienced by those using a non-MS implementation without the extensions) that start as annoyances gradually escalating, and at all times switching to the MS implementation is an easy (and, as long as their market share isn't dominant, affordable) option to make the headache go away.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: