4 ms·

This is a particularly bad example since the OOXML standardization process was fraught with issues and there are deviations between the standard and Microsoft’s

This is a particularly bad example since the OOXML standardization process was fraught with issues and there are deviations between the standard and Microsoft’s implementation. For starters, see https://en.wikipedia.org/wiki/Office_Open_XML https://en.wikipedia.org/wiki/Office_Open_XML

simion314 4y ago
So instead of something imperfect you prefer nothing, great I am sure Apple stuff is not perfect so don't use it. We use open source docx tools and write code to work with docx format so the actual reality is that it works infinity times better then attempting to reverse engineer some proprietary binary stuff . People would make open sourse stuff to connect to Apple things and if Ap[ple is as bad as Microsoft we can call them out and try to do our best with or code to workaround the imperfections.
- stevewatson301 4y ago
  For the trivial case where a document or a spreadsheet with just some text has to be exported out of a system, it works. But there are other formats such as CSV that already exist for this purpose and have a higher degree of. My point wasn't about writing to those formats for these basic use cases, but rather about building interoperable applications that can both read and write from the format. Since the spec is relatively loose and Microsoft hasn't adhered to it well, there are many issues when you use something like LibreOffice. And whether you like it or not, people do like using the advanced features of the Microsoft Office suite.
  - simion314 4y ago
    But what is your point, the MSis good and people forcing interoperability are bad? Google Docs and other open source tools can import docx and this is great even if not perfect, and if there is an issue you can read the code of the document and maybe figure the problem, is Infinity times better then the old ways where Word would probably just binary serialize the data and dump it in a file. We are talking about giants having to interoperate with others, what is your point? It can't be done perfectly because giants are evil and we should not try?

simion314 4y ago

So instead of something imperfect you prefer nothing, great I am sure Apple stuff is not perfect so don't use it. We use open source docx tools and write code to work with docx format so the actual reality is that it works infinity times better then attempting to reverse engineer some proprietary binary stuff . People would make open sourse stuff to connect to Apple things and if Ap[ple is as bad as Microsoft we can call them out and try to do our best with or code to workaround the imperfections.

stevewatson301 4y ago
For the trivial case where a document or a spreadsheet with just some text has to be exported out of a system, it works. But there are other formats such as CSV that already exist for this purpose and have a higher degree of. My point wasn't about writing to those formats for these basic use cases, but rather about building interoperable applications that can both read and write from the format. Since the spec is relatively loose and Microsoft hasn't adhered to it well, there are many issues when you use something like LibreOffice. And whether you like it or not, people do like using the advanced features of the Microsoft Office suite.
- simion314 4y ago
  But what is your point, the MSis good and people forcing interoperability are bad? Google Docs and other open source tools can import docx and this is great even if not perfect, and if there is an issue you can read the code of the document and maybe figure the problem, is Infinity times better then the old ways where Word would probably just binary serialize the data and dump it in a file. We are talking about giants having to interoperate with others, what is your point? It can't be done perfectly because giants are evil and we should not try?