3 ms·
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 s
by michaelgrafl 9y ago
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.
- thearn4 9y agogit + 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.
- mynewtb 9y agoMuch 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.
- Nullabillity 9y agoSo they finally managed to reinvent git blame?
- marcosdumay 9y agoYet, no two people manages to edit the same version of the file. Current change integration tools each lack on their own way.