Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali...
by curiousgal on Monday May 29, 2017 @02:34PM
(#14440611)
I remember coming across a comment from someone who worked on Word in the past. Most of the engineers don't know how it works and are scared of breaking backward compatibility.
[ Parent
| on HN ]
Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali...
by izacus on Monday May 29, 2017 @03:57PM
(#14441091)
That engineer doesn't work on Word (he worked on WordPerfect) so not knowing how a proprietary format of another company works isn't really surprising :)
Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali...
by pbhjpbhj on Monday May 29, 2017 @03:31PM
(#14440948)
I wonder how much of that is due to Microsoft making their file format opaque to enable vendor lock-in?
Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali...
by WalterGR on Monday May 29, 2017 @06:47PM
(#14441922)
Opaque in what way?
Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali...
by ethelward on Tuesday May 30, 2017 @06:02AM
(#14444113)
In the “some old versions are practically a memory dump” way. Interesting links in the SO thread below.
https://stackoverflow.com/questions/124869/how-does-the-doc-...
Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali...
by WalterGR on Tuesday May 30, 2017 @12:16PM
(#14446352)
Ah, I recall that now.
The complexity is explained, and it's not due to an attempt by Microsoft to encourage vendor lock-in. I'm curious of the commenter I replied to above has evidence to the contrary.