News for hackers. Stuff that matters.
Re:The LaTeX Fetish (2016) by moomin on Monday August 14, 2017 @02:47AM (#15006966)
So, to demonstrate how bad LaTeX is, he picks the single most markup heavy thing you do (barring tables) and compares it to plain text? Plain text, I'll point out, that doesn't format the same way. In practice, there _are_ a bunch of extra steps to get this working in Word, they're just not easy to express in a text document.

Then he goes on to show the example of trying to find a spelling error. Ignoring that this just demonstrates his editor support isn't as strong as word's. And completely elides the cascading nightmare that is what happens when Word formatting goes wrong.

Someone else has already pointed out how much superior a text based format is if you want to work with multiple people or track the history of a document.

WYSIWYG editing has, to my mind, one advantage only: it's easier to get started. LaTeX has its disadvantages (such as being a macro language) but being a markup language isn't one of them.

Re:The LaTeX Fetish (2016) by peterburkimsher on Monday August 14, 2017 @04:21AM (#15007258)
> work with multiple people or track the history of a document

I often proofread for my friends. I tell them that they must use Track Changes in Word. Is there a better tool that you recommend?

Re:The LaTeX Fetish (2016) by LeifCarrotson on Monday August 14, 2017 @08:30AM (#15008152)
Google Docs supports multiple simultaneous editors and tracks revision histories. It was a lifesaver for group projects in college.

And while 'always online' is often a bad thing, it seems to be a lot more reliable than the alternatives of email chains with the attached Word document, appending -R3-edited-complete-final-done.docx to the filename, the manual merges when two people are working on the same thing, or the USB stick that gets passed around.

Re:The LaTeX Fetish (2016) by raarts on Monday August 14, 2017 @07:59AM (#15008033)
Word change tracking is for word users like democracy. It's a bad system, but all alternatives are worse.
Re:The LaTeX Fetish (2016) by Ar-Curunir on Monday August 14, 2017 @05:19AM (#15007434)
LaTeX + git
Re:The LaTeX Fetish (2016) by moomin on Monday August 14, 2017 @06:58AM (#15007790)
It would be interesting if someone could write a program that could diff two LaTeX documents and produce a change-tracked version showing insertions and deletions.

I think it's doable, but it's a serious project.

Re:The LaTeX Fetish (2016) by rerx on Monday August 14, 2017 @07:07AM (#15007831)
It's done and it works very well (in my experience) for comparing two revisions of a document: https://www.ctan.org/pkg/latexdiff
Re:The LaTeX Fetish (2016) by geezerjay on Tuesday August 15, 2017 @04:19AM (#15016391)
Plain old diff does just that.

I'm assuming that what you're actually asking for is a pretty GUI that pretty-prints diff's output.

Re:The LaTeX Fetish (2016) by torchous on Monday August 14, 2017 @07:19AM (#15007884)
Re:The LaTeX Fetish (2016) by axelf4 on Monday August 14, 2017 @10:06AM (#15008623)
Being a text format means that you can use version control effectively. Latexdiff can generate diffs between versions. Wouldn't call it better, just different.
Re:The LaTeX Fetish (2016) by TrickyRick on Monday August 14, 2017 @06:24AM (#15007654)
Sharelatex if you want something that's easy to get started with for non-programmers (As opposed to Git)
Re:The LaTeX Fetish (2016) by panglott on Monday August 14, 2017 @08:43AM (#15008207)
To demonstrate what a barrier LaTeX is, he illustrates by writing the title of a paper, the author, date, and first line. The result is obviously human-readable in a word processer without special training, but not in LaTeX.
Re:The LaTeX Fetish (2016) by geezerjay on Monday August 14, 2017 @04:07PM (#15012334)
> he illustrates by writing the title of a paper, the author, date, and first line. The result is obviously human-readable in a word processer without special training, but not in LaTeX.

And that shows, at best, that if all you do is write papers with the author, date, and only thefirst line, then perhaps Word is better suited for that particular task.

But then, writing real documents is far more demanding than that.

For instance, let's say you're trying to publish your paper in a document, and your paper has more text than a single first paragraph. You find out that the style guide imposed by a journal demands that all your figures are placed at the end, in annex. In LaTeX, all you need to do is add a single line of text (include a package). How much work does Word forces you to do?

And I won't even get started on the fact that MS Word fails to support any vector graphics format.

Re:The LaTeX Fetish (2016) by moomin on Monday August 14, 2017 @10:26AM (#15008755)
Show me the person who can't answer the question "Who was the author of the paper?" by reading the LaTeX version and I'll concede you have a point.
Re:The LaTeX Fetish (2016) by panglott on Monday August 14, 2017 @11:49AM (#15009521)
The person first has to realize that it is an actual paper that they are supposed to be reading, instead of some kind of mangled file.
Re:The LaTeX Fetish (2016) by moomin on Monday August 14, 2017 @12:46PM (#15010128)
I think you're making it harder for yourself, not easier. Now you're assuming the following:

1) The person has no knowledge of LaTeX 2) They've never seen a markup language before 3) Yet somehow they've received this file, devoid of context, instead of the PDF, and they've opened it up in a text editor. And somehow this is relevant to something they're doing.

Who is this person? What are they doing? How is their experience worse than the guy with no experience of Word, no knowledge of Word who opens up the equivalent Word document in vi?

Re:The LaTeX Fetish (2016) by pantalaimon on Monday August 14, 2017 @03:48AM (#15007178)
I must admit that getting text to flow around images has always lead to cascading nightmares for me in LaTeX too.
Re:The LaTeX Fetish (2016) by TrickyRick on Monday August 14, 2017 @06:25AM (#15007661)
Doing anything with images is a cascading nightmare. Thankfully the ratio of images to text in the articles I've written in Latex has heavily favored text and after a while you gather a collection of snippets for displaying images in a few common ways.
Re:The LaTeX Fetish (2016) by geezerjay on Tuesday August 15, 2017 @04:24AM (#15016408)
> getting text to flow around images

In general, either your images are too large when compared to the text column length, or you're trying to force text around an image when it doesn't belong there.

Usually, type-setting principles tend to place figures at the top of the page or in dedicated pages, the later due to its cost-cutting advantages. Somehow, people assume that an indeterminate-size figure can be placed anywhere without it affecting the text's readability

Re:The LaTeX Fetish (2016) by madez on Tuesday August 15, 2017 @06:02AM (#15016823)
I like having pictures in a text, and exactly where they are referenced. If an image is not necessary for the text, then leave it out, or put it into the annex.