News for hackers. Stuff that matters.
Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali... by michaelgrafl on Monday May 29, 2017 @01:34PM (#14440269)
I will happily use Markdown for my own writing. But I would never use Word for that anyway.

What I use Word for is at Work, mainly for sending back and forth specs with an update history and annotations. I do not even read documents in Word. I “check out“ the version of a spec that I need, save it as a PDF and open it in Sumatra.

I am sure there are better tools for this. There must be, because the process sucks. But customers do it this way and I am sure it makes them jizz their pants, because if you are not enthusiastic about tools in general and know very few tools other than MS Office, it must actually seem cool and pro to be able to do it like that.

I would push better tools on customers if I would have to spend more time on reading specs. But I do not, so I will not. And Libre would not make for a improvement.

Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali... by thearn4 on Monday May 29, 2017 @01:49PM (#14440364)
git + markdown could be an interesting combo for back and forth written revisions (we do it at work with latex and git for research papers). But to someone outside of the tech community, it looks 100% alien of a workflow.
Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali... by mynewtb on Monday May 29, 2017 @02:20PM (#14440535)
Much much too awkward to use. Word processors show changes of different authors in different colors, allow dynamic history, discussing proposed changes etc etc. All in an intuitive, graphical interface.
Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali... by marcosdumay on Monday May 29, 2017 @03:16PM (#14440865)
Yet, no two people manages to edit the same version of the file.

Current change integration tools each lack on their own way.

Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali... by Nullabillity on Monday May 29, 2017 @02:30PM (#14440584)
So they finally managed to reinvent git blame?