Hacker News Reader

Comment by xattt | Hacker News Reader

> I thought everyone on academia used LaTex…

LaTeX absolutely sucks for proofing. Typos end up being buried in tags, and you end up with a document that looks pretty but possibly not fully edited.

If you are collaborating with advisors, they may wish to add comments to your copy as you work through your thesis. There is no clean way to do this in a TeX source file, so the only way to do this would be to export your work-in-progress into a DOCX, and then work your changes back into your source.

Versioning-by-hand sucks balls. When you’re approaching various deadlines with other obligations at hand, all open-source kumbaya ideas go out the window and you just make do.

For your manuscript_final_FINAL_v2.docx file, manual layout tuning ends up being not too bad and likely takes less time than troubleshooting LaTeX which might not have as much documentation.

View on HN

Last time I wrote anything remotely academic was several decades ago, but at that time, the argument was that you had to use LaTeX because Word documents had no support for simultaneous editing, version control, and editors comments. It is truly bizarre to see the same arguments repeated after so long time but completely reversed, in favor of Microsoft Word. Surely the tools haven't become worse over time, given the popularity of github, Overleaf and such?

Don't most people use git for their latex (or even markdown) version control? All the tools that have been developed for code collaboration work really well for documents compared to messing around with word's undocumented format and binary blobs.

In academia (at least in fields that primarily use LaTeX) most people just use Overleaf.

No, git is understood as an unreasonably difficult Dropbox for most people that do not code substantially.

I use Markdown + Pandoc compiling to a .docx as a workaround, but merging changes back is manual.

Disagree. Hunspell and aspell have tex modes that understand well what needs to be checked and what doesn’t.

Comments can be added with ‘%’. Just make sure to have a linebreak at every sentence and it’s cleaner than anything. Services like overleaf also exist for collaboration.

You can use any versioning system you want. From git to dropbox, its plaintext.

I do agree that layout can be very time consuming, but it helps once you learn to not care about it till the absolute end of working on the content.

It isn't realistic to teach your collaborators a new system just for your own comfort. They'll just avoid making edits/comments. Especially if you're just a PhD student/postdoc interacting with a full time scientist - who will have much more work to do than fiddling around with your esoteric editing system.

It's kind of the same issue that FOSS enthusiasts often miss regarding other things, eg. most gamers wouldn't waste their time fiddling around with WINE settings to get things to run in Linux, the solution wasn't to tell them to just install something extra and do things different, it was to improve the infrastructure such that very little fiddling is needed in most cases.

Sure, I did my phd back in the 2010s and latex+git/svn was what everybody used. Im not saying you cant use word, im just saying the criticism raised of latex above is not a valid reason to.

Reply on news.ycombinator.com