Sometimes I wonder who's paying for all these shill commenters
1. This is a ridiculous statement, and you're not being honest about the legitimate problems we've faced as a community. You also are not accounting for the diverse set of opinions in the community, not everyone supports every project's implementation decisions.
2. The classic Microsoft problem is simple, they promoted proprietary closed standards.
- Microsoft Proprietary standards were closed, so intensive reverse engineering is required for any interoperability.
- Microsoft Proprietary standards were proprietary, so you could sued for violating patents/copyrights even if you used/created a clean-room implementation.
- Microsoft Proprietary standards were de-facto standards, by being used by Microsoft, they are extremely influential and thus these problems are solidified.
Now they released their OfficeOpenXML standards, and while many would say they should have just used ODF, at least the standards are open and don't present the old type of problems. So you see, if the community wanted to support these new standards, they could always create their own implementation. Sure it's extra work, but it's not near the level of reverse engineering, and sometimes new standards are legitimately required. I'll leave that to the masses to decide legitimacy, but nothing prevents the new interfaces and API's from being codified.
Originally posted by nslay
View Post
2. The classic Microsoft problem is simple, they promoted proprietary closed standards.
- Microsoft Proprietary standards were closed, so intensive reverse engineering is required for any interoperability.
- Microsoft Proprietary standards were proprietary, so you could sued for violating patents/copyrights even if you used/created a clean-room implementation.
- Microsoft Proprietary standards were de-facto standards, by being used by Microsoft, they are extremely influential and thus these problems are solidified.
Now they released their OfficeOpenXML standards, and while many would say they should have just used ODF, at least the standards are open and don't present the old type of problems. So you see, if the community wanted to support these new standards, they could always create their own implementation. Sure it's extra work, but it's not near the level of reverse engineering, and sometimes new standards are legitimately required. I'll leave that to the masses to decide legitimacy, but nothing prevents the new interfaces and API's from being codified.
Comment