Reach for Markdown, not LaTeX (jez.io) 267 points by sridca on Feb 17, 2018 | hide | past | web | favorite | 178 comments

 Author here! I'd like to take a second to point out that the audience I had in mind when writing this article was mostly my fellow classmates in college. In school we were hastily introduced to LaTeX freshman year and were required to typeset our homeworks before submission.The point of the article isn't "you should never use LaTeX" but rather "hey, there's this other, simpler tool that you might like better!" plus some starter templates to make the transition easier.Importantly, I encourage everyone to use the tools that they feel most comfortable using!
 I'd also add that while Markdown and LaTeX can do some of the same things, they're designed toward very different tasks. I've used both numerous times in my career, and I can't remember a case where it's been ambiguous which tool was more appropriate for the task.If it's going to be printed, you probably want LaTeX. If it's going to be rendered to a screen, you probably want Markdown. If it's going to be rendered to a screen and have math in it, you probably want Markdown with some LaTeX for the math. If it's going to be rendered to a screen and printed, better start looking for a job, because that project is going down in flames.
 (In addition / As an alternative) to Pandoc, has anyone tried Bookish [0] by Terrence Parr of ANTLR fame?It was referenced by Jeremy Howard in a HN comment [1] on the submission for their "Matrix Calculus for Deep Learning " HN submission of 18 days ago [2]:>Jeremy here. Here to answer any questions or comments that you have. > >But more importantly - I need to mention that Terence Parr did nearly all the work on this. He shared my passion for making something that anyone could read on any device to such an extent that he ended up creating a new tool for generating fast, mobile-friendly math-heavy texts: https://github.com/parrt/bookish . (We tried Katex, Mathjax, and pretty much everything else but nothing rendered everything properly). > >I've never found anything that introduces the necessary matrix calculus for deep learning clearly, correctly, and accessibly - so I'm happy that this now exists.
 FYI bookish embeds math formulas as vector images (SVG) to the generated HTML.
 When you say "rendered to a screen", do you really mean "placed on a webpage"? PDFs generated by LaTeX are rendered to screen all the time.edit: Actually, I find that I completely agree with your point if "printed" is replaced by "shared in pdf format" and "rendered to screen" is replaced by "shared in plain text or HTML format".
 You can simplify it even further:Will the content be shown with fixed line lengths, or with responsive line lengths?
 I'll have to think about this further, but at first glance this seems like a better heuristic than what I wrote.There's a little bit of opinion embedded in my original post, which is that PDF is an inappropriate format when intended for screens. It's okay if you're wanting to provide a primarily printed document on the web or in email, it's okay, but if your primary target is screens, PDF provides a pretty poor user experience.
 If you haven’t tried it yet, I encourage you to give Markdown + Pandoc a try for printed docs. Pandoc can take a LaTeX template and flow Markdown into it. I find Markdown formatting simpler to remember and execute than LaTeX, and there are a huge number of editors and live-preview apps that will let you validate your Markdown as you write. A few keystrokes, and you get a beautiful PDF document, flawlessly typeset in Computer Modern - and with a few more keystrokes, you can have an HTML page with exactly the same content.There is even a company, LeanPub, that is based on generating paper and e-books direct from Markdown.
 Makefiles address that. make html pdf  This one has many OSXisms & wants some homebrew bits, but may give you a starting point:https://pastebin.com/raw/H43MKTCqReferenced utility script:
 Yup, having a default Markdown doc project that you clone is a big help. That way, you can include a Makefile, as well as embed LaTeX header info.For cases where you really need to share your doc with coworkers in an editable form, you can even define an MS Word target...
 That's among the targets here.
 While not exactly the simplest tool around, org mode is still a lot simpler than LaTeX and brings excellent export features to both LaTeX/pdf and html. It’s probably a hard sell for anyone who doesn’t use Emacs already, but for someone already using Emacs, it’s quite neat. I’ve found that for me, it offers the right balance between simple basic functionality (like Markdown) and optional advanced features.
 > If it's going to be rendered to a screen and printed, better start looking for a job, because that project is going down in flames.What makes you say that? I'm just finished up my first published book. The entire thing is in LaTex, which is extremely powerful. With conditionals and macros etc. etc. So I make a print-ready pdf and I'm good to go.I run the whole thing through pandoc and it spits me out an ePub that's good to go for the eBook version.Works a treat. I do battle LaTeX some days, but the results are gorgeous.
 It's mostly a joke. I've worked on a few things that "needed" to be PDFs with links inside them, because the clients couldn't decide whether they wanted a print version or a digital version, and went with "both". I won't write off the idea that it can be done usefully, I've just never seen it result in anything but a bad user experience for both use cases.I'd agree your use case is a good one for LaTeX.
 Why is LaTeX unambiguously better for print? Is it just the support for math notation, or is there more to it?And since "print" very often means a PDF that's also available online, has there been any progress on tagged PDF support in pdflatex or a similar tool? This is important for accessibility.
 Have you ever tried to typeset a complex document with side bars, figures, multi-part figures, figures that contain math (not just images), and layouts that take a lot of tweaking to get just right?I can imagine doing that in Pandoc Markdown, but only with extensive use of raw LaTeX code. Most of the above doesn't have a direct equivalent even in richer Markdown dialects like Pandoc.
 Ah, thanks for educating me. I pity anyone who has to work within the constraints of print in 2018. To me, hypertext that adapts to the user's device and needs (e.g. rendering at a different font size and reflowing appropriately, or rendering through non-visual means like speech and braille) is the only way to go these days.
 To be fair to latex, the majority of hypertext examples don't do any of those things either.
 It's harder to make fine adjustments, such as those made by the microtype latex package.
 Aside from what other commenters told you: LaTeX just typesets better, meaning that it will choose line-breaks, inter-character and inter-word spacing, ligatures, hyphenation, etc. much better than your regular browser.Try justifying text on a relatively narrow column in HTML, and then try it with LaTeX. There's a world of difference in readability between them.
 > Why is LaTeX unambiguously better for print? Is it just the support for math notation, or is there more to it?LaTeX is techniques and heuristics from hundreds of years of typesetting for print, codified into a program.HTML is at most 29 years old, and has only supported typesetting of any kind for a fraction of that. What typesetting capabilities it supports are designed by committees, and its primary purpose has always been screen display, never print.In the simplest/best case, LaTeX will simply produce nicer-looking results for print. In more complex/worse cases, LaTeX can do things that HTML in a browser can't reasonably do at all for print, even with CSS.> And since "print" very often means a PDF that's also available online, has there been any progress on tagged PDF support in pdflatex or a similar tool? This is important for accessibility.I can't answer this question directly because it's been a while since I attempted such a thing, but this is largely what I was joking about with the "the project is going down in flames" bit in my previous post. If you are concerned about accessibility, targeting a proprietary format that resists parsing for text-to-speech or fragment translation and doesn't support variable-width lines for screen readers is a bad idea. Tagged PDFs are really just a hacky attempt to fix the problem: HTML was designed with accessibility in mind from the beginning (though admittedly HTML/CSS/JS as used by modern websites do a very poor job of providing accessibility). Maybe there has been progress in adding this to pdflatex, but it's still a bad idea.
 Knuth said that doculents should be readable, but artvto be hanged on a wall.Typesetting my thesis in LaTeX (physics, 2000) was an amazing choice. I could hardly modify anything (it is doable but requires a lot of work and in the meantime you learn that the default is better) so I was left with the content.I knew that it would just work and took from me all the philosophical sufferingbof choosing such and such fontvsize for the title of adjusting margins, or placing a graph.
 I've done the latter, but basically it's been luck that the program I used (Pages 09) works for print, and also copy/pastes decent html.Currently jerry-rigging a script to get html out of it by pasting the scrivener and exporting, while keeping pages 09 for print.It....works, but I would not recommend it unless you have a clear reason to do both. And I'd recommend another program, as pages 09 will eventually be made incompatible on mac.
 “If it's going to be rendered to a screen and printed, better start looking for a job, because that project is going down in flames.”Ah that explains what’s going on at Safari Books...
 I have used latex to typeset most of my work at uni. but recently I began using org-mode, With a bit of knowlegde it is so much easier to structure my notes. And then it can export to a lot of differnt formats like latex.
 Yep, org-mode is really cool too!
 I'm a bit confused by this. As I see it, LaTeX can do everything that Markdown can before things get complicated. Where LaTeX does get complicated (e.g. when designing figures or drawings), Markdown doesn't offer any advantage or even any functionality. For composing simple documents or outlines and doing typesetting of equations, LaTeX has some boilerplate but it's really not that much.
 LaTeX in my experience, is worse than markdown for one crucial use case: formatting code. Formatting large blocks of monospaced text (especially monospaced text that includes character sequences that can be interpreted as LaTeX commands) has always been kind of a chore. In markdown, on the other hand, it's as simple as enclosing the text between two sets of triple-backticks ().
  \usepackage{listings} \begin{lstlisting} your code here \end{lstlisting}  That's not much harder, is it? Plus, it has a ton of other functionalities you might want.
 Now add syntax highlighting. In Markdown, it's trivial (language-name), in LaTeX, you're going to have to define a style. LaTeX is more flexible, but it does come at a cost.
 Maybe you should take a look here and disabuse yourself of that idea: https://en.wikibooks.org/wiki/LaTeX/Source_Code_ListingsRelevant bit: It supports the following programming languages: ABAP2,4, ACSL, Ada4, Algol4, Ant, Assembler2,4, Awk4, bash, Basic2,4, C#5, C++4, C4, Caml4, Clean, Cobol4, Comal, csh, Delphi, Eiffel, Elan, erlang, Euphoria, Fortran4, GCL, Gnuplot, Haskell, HTML, IDL4, inform, Java4, JVMIS, ksh, Lisp4, Logo, Lua2, make4, Mathematica1,4, Matlab, Mercury, MetaPost, Miranda, Mizar, ML, Modelica3, Modula-2, MuPAD, NASTRAN, Oberon-2, Objective C5 , OCL4, Octave, Oz, Pascal4, Perl, PHP, PL/I, Plasm, POV, Prolog, Promela, Python, R, Reduce, Rexx, RSL, Ruby, S4, SAS, Scilab, sh, SHELXL, Simula4, SQL, tcl4, TeX4, VBScript, Verilog, VHDL4, VRML4, XML, XSLT. For some of them, several dialects are supported. For more information, refer to the documentation that comes with the package, it should be within your distribution under the name listings-*.dvi. Notes 1 It supports Mathematica code only if you are typing in plain text format. You can't include *.NB files \lstinputlisting{...} as you could with any other programming language, but Mathematica can export in a pretty-formatted LaTeX source. 2 Specification of the dialect is mandatory for these languages (e.g. language={[x86masm]Assembler}). 3 Modelica is supported via the dtsyntax package available here. 4 For these languages, multiple dialects are supported. C, for example, has ANSI, Handel, Objective and Sharp. See p. 12 of the listings manual for an overview. 5 Defined as a dialect of another language  If you want to get fancier, and have pygments in your system, you can use the minted package, instead.
 Ah, seems like the situation is better than I remembered. I confused colored syntax highlighting with the default settings, which highlight using font weight/italicness etc.I did try minted once, but never used it in practice. The dependency on pygments making the documents more system dependent is less than ideal.
 You can of course redefine the default style if you don't like it, but that is no more work than doing the equivalent in CSS (I guesS?) for whatever MD renderer one uses.I agree that pygments adds a bunch of dependencies, which may be too much just to get some colored syntax highlighting.
 If you can type  without breaking your hand. is a three-key combination AND a dead key on non-US keyboards.
 That's very easy by using the minted package, and even in Debian, it is installed by default: \begin{minted}{python} def square(x): return x * x \end{minted}  Does not look difficult to me.
 I'm not sure... I think you raise a good point, and I would have the same thing as you before I started writing in Org and exporting to LaTeX, instead of a) writing in LaTeX directly, or b) drafting/outlining in Org and rewriting the final copy in LaTeX. Now I think exporting from Org is so much easier.
 I can second this. Markdown and Pandoc work quite well together. I write documents professionally using this setup.I do fall back to LaTeX for certain formatting, but it's actually quite easy to build pass-through filters so that raw LaTeX can be inserted when specialized formatting that can't be easily simulated in Markdown is required.
 I'd be very interested in any details of your approach that you could share. I added another comment to this thread with the details of what I've been working on for professional spec documents with markdown and rendering to PDF (testing with CSS now).
 It's relatively low-tech, but it does work. First, I have some scripts to preprocess the Markdown and extract custom markup that I have built to do things that Pandoc's Markdown can't, but that I can still easily inline in the document. For instance, I replaced the source code markup with a custom one that generates LaTeX formatted the way I want it formatted. I use Pandoc to output LaTeX. I then have a series of shell scripts to postprocess this LaTeX to insert pre-rendered figures, re-introduce the custom markup as rendered LaTeX, or to massage the output so that the document is laid out the way I expect.I'm planning to use this to write a book in the near future.
 I was also required to typeset homework for some classes in college, but I used LyX [1] instead and never really learned how to typeset a whole document. I picked up the equation syntax though.
 LaTeX equation syntax is a gateway drug to heavier typesetting systems. I also started out at maths pastebins when wanting to explain things to others in a readable way.
 Interesting, and a bit surprising. Back in the Triassic Age, I picked up LaTeX from an undergrad roommate because it was easier than writing up homework by hand, and because you can turn a basic ".txt" file into a ".tex" file with very few changes.I agree that Markdown and friends have their place, but they quickly reach their limits. You write that "Pandoc can take care of the presentation for us," but in my experience, Markdown and such will only get you as far as "good enough." If you want to typeset complicated equations, or print something more complicated than a novel, you need more powerful tools.
 You can write markdown and pandoc will leave any latex fragments for the backend. This only works for latex based backends like pdf but it works great if you have some formulas.Code formatting and tabels are also vastly easier with pandoc.
 Yeah, LaTeX tables are a pain, so I usually generate them with a script and include them via "\input{...}". But I've come to rely on TeX macros to generate repeated things like fancy chapter intros, and on packages to customize page headers, etc. This stuff is not necessary for a homework assignment, but I doubt it's as easy to accomplish in Pandoc.On an unrelated note, I hadn't checked out Pandoc's output in awhile, and this bit from http://pandoc.org/demo/example13.pdf looks pretty bad: https://i.imgur.com/Kxy4mic.png . Granted, the terrible word-breaking and spacing is TeX's fault, but typesetting usually seems to require dealing with a few special cases by hand. I wouldn't trust Pandoc, or any other program, to "take care of the presentation" without a bit of hand-holding.
 When I was in uni I used Latex to format work that had math and needed better organization (theses, publication papers). For simpler stuff like comp sci assignments I did it in markdown and ran it through pandoc.
 Thank you for the clarification. This should be top posted to avoid a lot of the posts that have already occurred. LaTeX is far more encompassing than Markdown will ever be.
 Markdown can do quite a lot, but it doesn't have any way to write mathematical formulae. Since that's 90% of why I use LaTeX in most cases it seems silly to recommend Markdown. LaTeX has a superset of features, and is well suited to what it does properly (typesetting). Markdown is quick and easy to use, so it's good for blog posts.
 Pandoc's tex_math_dollars, tex_math_single_backslash and raw TeX mode makes it possible to fallback to TeX whenever you need: https://pandoc.org/MANUAL.html#math-inputA Markdown -> LaTeX -> pdf pipeline was how I wrote all of my algorithm assignments in college. I wrote things like: * **Basis**. Prove for $n = 0$... * **Induction**. If \mathcal{G} is a graph ... $$...$$
 You seem to be well over half-way to LaTeX there, so what's the point in using markdown?If the verbosity of writing \begin{description} ... \item[basis]... \end{description} is the issue, you can get around that with a couple of shorthand macros.
 I wrote my math phd thesis in Markdown/LaTeX in this way.I also replaced all maths symbols with their Unicode equivalent. The result was very readable markdown source text, easily compiled to Latex and PDF, using a mk file.My thesis also included formalised proofs in a proof assistant, and they were just written straight into the markdown files as code blocks, and were using the same Unicode symbols as the rest.Later, when publishing the different parts of my thesis, this separation from Latex made it easier to convert to whatever cls the publisher wanted, since I would just change the template.
 I wrote mine in plain LaTeX, never had an issue with it. Regarding code, you can use the listings package (\lstincludelisting) to include source code files directly. I fail to see the interest in having a bastardized, not quite TeX, not quite MD file (unless you're using something like Org, of course, and using its other functionalities).Regarding having unicode for the maths, how did you deal with symbols that needed scaling (brackets, integrals, etc.?) They may look simpler when seen as text, but they certainly won't render nicely as math...
 I just make the symbols shortcuts for the commands. So for instance∑_{0≤n≤k}n²expands to\sum_{0\le n\le k} n^2.
 Do you have a library of these substitutions available? Sounds like it could be useful.
 I just have this[0], which is a list of the substitutions. You can either make it a sty file, or just stuff it in the preamble, or template.Some of these are suboptimal. But you can just change them, and make your own.
 Thanks!
 From my (limited) experience of writing a documentation page for a library I made, Markdown is pretty limited (speaking of CommonMark here). Even basic things like table or image need HTML to be done. The gain in syntax is lost on the coherence side as the document mixes two languages, and an additional step of processing the document is required to transform it in full HTML.It have it use cases but writing long and complex documents is not one of them.
 CommonMark _does_ support images: http://spec.commonmark.org/0.27/#imagesSome other, non-standard variants of Markdown also handle tables via a syntax which resembles ASCII art. And while that format does do an excellent job of adhering to Markdown's ethos of remaining readable in plain text; I usually prefer to use HTML fallback anyway as it's easier to maintain.
 The most commonly used Markdown variants (Github, So, Reddit, probably Slack) support tables, they've been in use for years and work well. I can't believe Commonmark can't just standardise what's already being used by the majority of users.Some of the suggestions in the discussion thread[0] don't pay any attention to this, and if they agree on something that nobody uses it'll just be ignored.
 Kramdown is far and away the best Markdown implementation at the moment. It doesn't have the problems you describe (but does others).
 My problem with LaTeX is that a ton of programmers think it's a good idea to use LaTeX instead of, say, Word or Writer or plain text wrapped at 80 characters or a Wiki for things like process or project documentation.Programmers love to use LaTeX, because they get to feel like they're doing something exciting like writing a computer program when what they're actually doing something incredibly boring like writing documentation. They get to use the same plain text editor they're familiar with. They get to use the same version control that they use with their code. I've seen programmers try to use many justifications for why LaTeX is important for their doc because LaTeX has some feature that everybody knows they don't actually need to use.The truth is that unless you have a literal need for actual true typesetting, you should absolutely not use LaTeX for documentation. The reason for this is two fold:1. "First, you need a properly configured LaTeX build environment," are never, ever the first words that anybody wants to hear when they need to read, update, modify, and manage documentation. Documents that are not going to be published outside the company should never require a build environment.2. No matter what your job is, you're not going to have it forever and someone will probably be in it after you. If all your documentation is written in LaTeX, then suddenly, "Ability to write, modify, and maintain LaTeX documents," is a mandatory requirement. That's a significantly higher bar than "Ability to write, modify, and maintain Microsoft Word documents." Congratulations, you just added significant complexity to your job for essentially no benefit to the company.The only time you should favor LaTeX is when you're writing a document that will be published and is essentially entirely text. You're a mathematician or some other discipline and actually need to write extremely complex symbology. You have extremely complex and numerous references to manage. You're writing a high level research paper. Congratulations! You're the intended audience for LaTeX.If you're a software engineer writing standard documentation, put the text editor down and use Microsoft Word. Documentation is meant to be read by everyone, not make you feel good about being forced to write it.
 Wow, this is just so far off the mark I don't even know where to begin. LaTeX excels in three areas that are crucial for writing complex documents -- cross references, citations, and indexing. You clearly have not had to endure the house of horrors that is the MS Word ToC, or trying to get autonumbering working as you wish for sections, figures, and tables, or managing a large (100s of pages) multipart document, or any one of a bazillion other little asspains that crop up when forced to use Word for a nontrivial task like maintaining documentation for a large complex project. And point #1 is a complete straw man, setting up a TeX env takes 20 minutes and the basic doc format has not changed since the 1990s at least.
 Anecdote about LibreOffice 4.2.8.2: Due to a bug, LibreOffice was generating incorrect page numbers in the table of contents of a 80-page document: some sections were 1 page off, even right after I clicked to manually regenerate the TOC.It was very frustrating, because I noticed it just a few hours before the deadline. To work around of this bug, I had to insert manual page breaks (mostly randomly), and I had to make the vertical margins of the TOC pages smaller.LaTeX has always generated the correct numbers in the last 25 years I've been using it. And if I got something unexpected, I was able to fix it for good (without document-specific hacks such as manual page breaks) by adding some macro calls. With LibreOffice and Microsoft Office, getting such a fix ready in 1 hour is hopeless for me, so I'll either miss the deadline or I hand in something incorrect and unprofessional.Also: LibreOffice doesn't support character formatting (of a few words only) in the ToC. LibreOffice doesn't support omitting a few select sections from the ToC. LaTeX supports both.
 I thought Latex was superior to Word in every way than I had a colleague that knew Word. Word if you learn it is just fine generating a ToC or autonumbering sections, figures, and tables.In practice, Markdown is better than either for documentation that isn't printed. It's easier to edit, can be viewed with a plain text editor, and has a minimal learning curve.
 > I thought Latex was superior to Word in every way than I had a colleague that knew Word. Word if you learn it is just fine generating a ToC or autonumbering sections, figures, and tables.No, it doesn't work well even if you know what you're doing. It's much better than when blindly trying to hack your way through, but there are still so many weird quirks it does which you always have to spend a lot of time on.
 I would say it works well if you know what you are doing, but in a shared document there is always some dumb ass in the team that does some manual formatting like using the bold-button instead of changing header type, or remove a link from an image. Then the all the references and indexes are beyond repair with the only way to salvage the document is to slowly, meticulously and painfully go through it in this outline-view and try to identify what should be a header and what should not.If only there was a way to create a Word document that forbids manual formatting it could actually be usable.
 "Word if you learn it is just fine generating a ToC or autonumbering sections, figures, and tables." : but can it do this? -- [Common Lisp Quick Reference](http://clqr.boundp.org/clqr-a4-booklet-all.pdf)
 Wow, that's beautifully set!
 > And point #1 is a complete straw man, setting up a TeX env takes 20 minutes and the basic doc format has not changed since the 1990s at least.Well, I had to re-encode my documents twice in that time, once to isolatin1, and once to Unicode, because I was writing in Spanish and German. But it was actually fun to figure how to make that translation happen completely automated and happen in a few seconds.
 You don't know the requirements of documentation that we're writing. They don't need a table of contents. They don't need an index. They don't need citations. They don't need math symbols. They don't need tables more complex than a word processor can create. We require no features which your typical academic or research paper requires. We are documenting processes with screenshots that users can refer to in order to accomplish specific tasks. Only a dozen of them are more than 25 pages, and in Word if you keep your document formatting simple and use the built-in styles for headings, the Navigation Pane serves as a hyperlinked ToC. None of these documents should be printed because the processes can change, so beyond basic structure, layout isn't particularly important.Furthermore, our documents can't be written in LaTeX because half the people responsible for maintaining them come from a non-technical background with no experience in programming. No, we are not going to inflict a WYSIWYG LaTeX editor -- all of which are far less usable than Word -- on people just because some technical people want to pretend they're programming.Nevertheless, our CS interns invariably say, "Why don't we use LaTeX for this documentation?" I understand why they want to. They use LaTeX for all their papers. However, it is inappropriate in our situation and has gotten to be a rather irritating question.
 > You don't know the requirements of documentation that we're writingYet you seem happy to prescribe your (extremely limited) views on everyone else without knowing their situation.Good for you if all your documentation requirements are trivial, and I'm sorry to hear that your team cannot cope with trivial software installs or simple markup. Maybe the problems lie not with LaTeX...
 Not many go into LaTeX "loving it". Many of us try Word first, and are just unhappy with its output. If you need something that is well typeset and don't want to spend a few $10k on professional typesetting software, LaTeX fits the bill well. Everything else about LaTeX is a pain, not a joy.Is a lot of documentation written in LaTeX? I would never use it for that. Paper that is going to be submitted to a conference? Sure! Blogpost? No, documentation that is read only online...also probably not. But I don't think I would use Word for that either, Word is a pain if you need something other than very standard formatting.  Back to my CS undergrad days, I wrote my assignments in LaTeX. It can handle practically every CS nerds: Complicated math expression? Check. Displaying beautiful pseudocode? Check. Binary tree? Check. Karnaugh map? Check. Etc etc.Probably you've heard that only real men write LaTeX using plain text editors. I'm not a real man enough, so IDE like TeXnicCenter or Texmaker is needed :pThese days, personally I use Pandoc or Halibut (https://www.chiark.greenend.org.uk/~sgtatham/halibut) for anything not complicated. Or if working on team, then 'unfortunately' MS Word. Well, not every of us are nerds :)  I used Texniccenter also, but I don't find that I use any of the markup help, I just like the syntax highlighting (these days I just use vscode). I try not to do anything complicated with LaTeX anymore, its just never worth the trouble.  > Is a lot of documentation written in LaTeX? I would never use it for that.No, we have CS interns from the local college who invariably ask about it. We only have them for a few months, so I've probably answered that question several dozen times in the past few years. I know they use LaTeX for their papers as required by their CS department, so I know why we get the question. I'm just tired of answering it.> Word is a pain if you need something other than very standard formatting.I don't disagree with that, but our standardized formatting is to use the default styles. Use Title for the doc title, use Heading 1 for each major step or process if the doc has more than one (most don't) and Heading 2 for each individual step. This means the Navigation Pane serves as your document navigation. Most of our docs are less than 20 pages or so (and most of that is screenshots).  The current version of Adobe InDesign costs$20/month on subscription. Used copies of older versions can be found for relatively cheap.I would advise anyone who values their time against using LaTeX for any document that doesn’t primarily consist of mathematical formulas.
 One practical advantage of using free tools is that everyone in your company can use it, you can write automation that uses it, etc. I'm not going to defend LaTeX in particular, but there's a lot of value into using something (like Markdown or reStructuredText or whatever) that anyone in your company can propose edits to, where you can automatically publish nicely-formatted (e.g. HTML) documentation when anyone in your company makes a change, and so forth.Another way of gaining this advantage is to use something you're already paying for like an internal wiki.
 I’m not recommending anyone use InDesign or similar tools for everything.It’s a typesetting tool designed for producing paper documents. You should use it for your company’s magazine, menu, posters, and published books, not for your auto-generated technical documentation, your blog posts, or your internal emails.The previous commenter wrote about what to do if you “don't want to spend a few $10k on professional typesetting software.” That’s much steeper than most people will spend on professional typesetting software.  Fair enough. My wife uses Adobe tools for typesetting, she is a professional (she pays$100/month for her CS subscription, however). I'm not a professional, I've looked at the amount of effort needed to refine output in these tools and they make LaTeX look usable...
 I find that in most cases InDesign takes an order of magnitude less time/effort and dramatically less frustration to get a particular careful output than MS Word, LaTeX, or other commonly available tools. Your wife probably has difficult requirements and exacting quality standards, and could likely get output with quality equivalent to common documents prepared using amateur/automatic tools in a much shorter time, if she wanted to.It’s almost impossible to do professional quality typesetting in MS Word. Last time I really tried was about 10 years ago. I spent like 4 hours trying and failing to fix basic typographic mistakes in another person’s 20-page document, and then gave up and did the whole thing over in InDesign in 20 minutes, with great results.In LaTeX, you can theoretically do anything you want but unless there’s already a template for it (or you have numerous or long documents targeting the same output style, for which you want to make a template and then mostly rely on automatic layout), it’s going to take a huge amount of time. It’s a good tool if you want output that is “good enough” for many practical purposes without direct human input, but it is especially difficult to do anything special-cased for a particular spread (moving images, text boxes, diagrams, ... exactly where you want them).LaTeX is great for things like auto-generated documentation, long structured outlines, legal documents, or math papers full of complicated formulas. LaTeX is abysmally ineffective for posters, magazines, or the like. I find that for the vast majority of content in between those extremes (e.g. college humanities homework, non-technical journals, resumés, menus, coffee-table books, novels, poetry, personal letters, ...), InDesign ends up giving nicer output with less headaches.
 In my field there are always templates. LaTeX, or I guess TeX, works well until it doesn’t, and then fails in ugly ways (quite the opposite of Word, which will work all the time not very well). So overflow and underflow paragraphs are possible, so are orphans, though it tries to avoid them if the output is decent. This is nice because I can fix all my problems usually by refining my content (changing words, orders, etc...), I don’t actually have to dig deep into TeX to otherwise modify the format! This is quite usable in general, though there are huge debates on whether it is appropriate.From what I can tell, Adobe follows the more technical approach, though I’ve only looked over my wife’s shoulder. The fact that I’m just producing PDFs with LaTeX is also different. If I’m writing a web essay, I don’t mind using straight HTML/CSS, even markdown doesn’t really convey many benefits for me.
 Web essays is definitely not the place to use professional typesetting tools. Browsers are simply incapable of doing professional quality typesetting of the type books have had since the 15th century because the output environment is too heterogeneous, unless you abandon html and render documents as SVG or PDF or something (I would not recommend doing that). Authoring tools won’t help you. On the web the best you can do is make (or purchase/find) a decent CSS template and hope it’s readable enough for most viewers on most devices.
 I've always been curious: Pretend I'm totally ignorant, and have no idea what need a typesetting tool fulfills. Someone who has used and been happy with Word / Open Office for years to write documents. What does LaTeX/InDesign solve for me, besides "nice looking math" that I'm not getting out of basic word processors? How do I know which one I need? I honestly have no clue. If I were to start writing a book tomorrow, I'd just open Word. Why not? What am I getting when I invest either the time to learn LaTeX or the money to buy InDesign?
 For writing a non-fiction book, you should probably use Word or something similar. Just make sure to avoid any formatting tools, only use semantic markup. Word is a pretty decent authoring tool. The end result can then be imported to a typesetting tool for formatting.InDesign is used when you need precise control of the output. For instance controlling exactly how figures are placed, you might more advanced control of how text flows between boxes, etc. It also has tools for very precise control of how the type is set, how big space should there be between letters and words, how should the right edge of columns look, should there be different number of columns on different pages, etc.Some of those things can be somewhat managed in Word, but you'll have to fight a lot of the automatic stuff, really not worth it if you are a full time design professional, much cheaper then to buy an expensive InDesign license.Latex is pretty good at having sane defaults. This was a bigger issue back in the days when the defaults of Word were frankly terrible. Today it's to a large extent about style choice. If you publish in an area where Latex dominates, the Latex styling will make your document appear as more serious. Latex also generally uses a more advanced type setting engine, for example it might join "fi" with ligatures etc. This can also improve the look of the document.Some people like the fact that you can manage Latex code as raw text. For instance using a VCS to manage version history. Word has some built in version management functionality, but it's quite clunky compared to Git.Personally I gave up on using Latex after my first master thesis and tend to use Word. I get too caught up in the formatting when I use Latex. Maybe it's too much power to handle for me?
 I just updated my resume two weeks ago. Too bad couldn't find the original LaTeX code, so I had to write a new one. I tried looking for some free MS Word templates, and didn't find anything fit.Curiosly, I found one while browsing at https://www.overleaf.com. LaTeX again :D
 If you're doing many one-off designs, I'm sure something like InDesign is faster than TeX. However, if you are producing similar-looking documents, the effort of writing your own LaTeX class is relatively low.There's also other advantage to using LaTeX, and that is the flexibility that comes with macros. Need to change some notation mid-way through your writing? It's trivial if you've used macros. Need to simplify some commonly used pattern? Define a new macro!Each tool has their place. Except Word, Word just sucks! (j/k, Word is brilliant when doing collaborative edits with non tech-savvy people, the track changes functionality is great, and not easy to replicate in other environments)
 I used to do all my docs in Adobe Framemaker. The output was amazing. The software itself felt a little obtuse, but seeing the printed pages was great.
 Since this is a forum that values reasoned debate, it would help if you actually argued against "They get to use the same plain text editor they're familiar with. They get to use the same version control that they use with their code." instead of just dismissing them out of hand. Those seem like important things!Also, what's wrong with apt-get install texlive-latex-recommended  (or better yet having your IT department / your provisioning system for new developer machines / whatever do that for you)? If your position was "Documentation edited by lots of people should not require weird CTAN modules," that I would agree with. You can write perfectly good documents of all kinds with just what's in texlive-latex-recommended.
 >Documentation is meant to be read by everyone, not make you feel good about being forced to write it.I think you missed the point you were trying to make here because nobody has any difficulty reading the PDFs rendered from latex.
 Yes, but maintaining documentation in PDF is not.Half the people that manage our doc are non-programmers. They're not learning LaTeX. They're not editing raw PDFs while the other half of the team uses LaTeX.
 Then you should have focused on maintainability in your comment, not legibility.
 I was with you until the last paragraph. Microsoft Word? Really? I can still read plain text documents written in the late 70s. Can't quite say the same for VIP-Writer. Or even Word Perfect.
 I'm sorry I disagree. Word is absolutely horrible for programmers to write in. It makes even the simplest of formatting repetitive and boring. It does not do automatic layout (things I DO NOT want to bother myself with) nor syntax highlighting.Just use Markdown if you're so concerned with people writing Latex.
 In addition to the other comments, being able to use version control on software documentation is a critical ability. If you develop software without a distributed version control system, you are just stuck in 17th century and there is no need to discuss further.If you use version control for your code and do not treat documentation as an integral part of the software which accompanies each version, this makes the impression that documentation is just an afterthought.To address the 'environment' issue, it is, in most cases, unproductive to not work on Linux where all of this stuff works out of the box.Also, your idea that it is easier to write a /good/ document using Microsoft Word than using LaTeX hugely underestimates the complexity of MS word for anything moderately complex, and even more hugely overestimates the complexity of using LaTeX for simple things. Somebody who has the job to write code in Python or Go should be easily able to document an API in LaTeX within two hours.And to add finally, maybe you don't believe the world will continue to move without using MS office. Be assured, there are quite a few large companies which have ditched office (say, Google) and this was not the slightest obstacle to their further success.
 Was with you until your recommendation for Word for documentation. Something like a wiki or Sphinx would be much more appropriate than a flawed and proprietary one.
 The proper tool is whatever the IT department has installed on everyone's computer by default, and failing that, something simple and easily edited (like raw text or markdown).I think the proper analogy is like editing documentation in PDF. Software that can edit PDFs is expensive and difficult to use, like LaTeX can be (difficult, not expensive, just in terms of time).
 Yes, though neither a wiki or text editor need to be installed, therefore even more accessible.
 Both your issues are solved by LyX. It removes most of the pain, and what remains tends to be with adding obscure document classes anyway, which you don't need for documentation.
 Or markdown or restructured text or ascii doc.I mean it’s not like it must be either LaTex or a word processor. Markdown is sufficiently easy to turn into text nowadays there’s really no reason not to first instance.And that’s assuming someone agrees with the general premise of this argument which I don’t think I do
 Do you think legal writing falls into this category?
 I have a dream where someone writes a processor that will allow the writer to bang out some Markdown-ish plaintext and turn it into a p&a with automatically generated Table of Contents, Table of Authorities, caption, and pleading paper.Call it LexDown or something even less mellifluous and free millions from the tyranny of Word style sheets forever.
 I was curious and searched if there was a project of that name already: https://github.com/OpenIus/lexdown
 You may be interested in Markua https://leanpub.com/markua/read
 As far as I'm aware, the vast majority of legal documents are still written with Word or Google Docs. Nearly everybody went to Word when WordPerfect died.
 Many flavors of Markdown support math extensions. Many do so in a way that degrades gracefully when the extended Markdown is opened in a standard Markdown tool.Typora is a great WYSIWYG Markdown editor that uses MathJax to render LaTeX mathematical expressions.
 The problem is, if you do a lot of formula writing in a narrative, most WYSIWYG editors that support LaTeX formula rendering are just not efficient. I want to type my thoughts, start a formula block, write my expression, end the block, and continue going. You can't do that in most WYSIWYG editors.
 You can definitely do that in Typora (unless I miss something what exactly you meant).
 When I think of WYSIWYG editors, I see presentation and content being mixed.Unless Typora has figured out how to get remove the need to locate the insertion point of a formula, open an editor, then submit the data to render an image that is placed inline or made into a block. If it has figured that part out then props to them for making it easier to write mathematics in an accessible editor.
 For formulas it just re-renders formula as you type it, no WYSIWYG magic where it's over-complicated. For regular Markdown it's WYSIWYG.
 I just wanted to thank you for this discovery.I am in the middle of writing a document and gave Typora a try, seems to fit the middle ground between "basic" formatting and Latex.
 I use RStudio with knitr when it is the wrong tool, because it is just too easy to make something that is easy to read and people think I put a lot of effort into formatting. I do have a few templates that I use so that the text isn't always Computer Modern, but it is mostly a mix of Markdown, Latex math, and features from R like kable for making tables. I even tend to plot graphics into the text using R, rather than looking up how to place them using markdown.
 This is what I do, too, except I use Org instead of knitr, because it lets me embed many more languages than just R. I should finish the blog post about this at some point...
 I don't get it. Say I already know that I'll need some formulae in my document. Then the use case here seems to be, essentially, that I can write # Section Name  instead of \section{Section Name}  and that I can write *important stuff*  instead of \emph{important stuff}.  I can see that the markdown version is a little nicer on the eyes and keyboard, but only by a small margin.Now, if I write a document in latex I need to understand exactly* latex.Latex is a beast, but there are no serious alternatives to typeset formulae.If I want to write markdown with some latex in it, I need to understand* markdown* latex* how pandoc interleaves the two.What if, as will inevitably be the case, something breaks? There will not even be close to as much documentation for the markdown+latex+pandoc stack as for the latex-only stack out there. Is there even a standard for markdown+latex, the pandoc way?Then there's the issue of packages needed to compile. Tex suites are already huge pieces of software. Now I also need to have pandoc. Pandoc is written in haskell, and the haskell stack on arch is a complete clusterfuck. I will not have saved time if I need to understand how to fix pandoc if it breaks after an update. Granted, this is mostly an arch issue, but the point is that the more software you use, the more likely it is that something breaks.The bottom line is that you replace an already complicated piece of software with the exact same piece of software and then something. I find it hard to justify it in this case where there is so little benefit.
 > Latex is a beast, but there are no serious alternatives to typeset formulae.People keep repeating this like it's true, but MS Word has had an excellent formula editor for a decade now (the one they shipped before Word 2007 was terribly shitty though).It's wysiwyg (which is fantastic if you're editing a big formula), it supports all math notation I've ever needed, and it has surprisingly decent UX. It even supports LaTeX-like input, eg if you type e^2 it gets autocorrected to e².This makes entering formulas as fast, if not faster, than LaTeX and editing formulas an order of magnitude easier because you don't need to re-parse that backslash-curly-mess that you entered a week ago. Just point and click and edit.
 It's nowhere near as nice in my, and lots of other people's, opinion. Just because people don't like it doesn't mean they haven't used it. Also, word's actual typesetting can't touch latex. I wouldn't want to use word for anything, let alone something that requires a large equation.
 Ah, and to add, if one wants to try re-formatting a Word document in LaTeX: One can import the word format to AbiWord, and export it to LaTeX. It will probably need a bit of clean-up, but it is easier to add things like footnotes, section references, a bibliography, or an index. So, for learning LaTeX, it might be a nice strategy to take a modestly-sized Word homework document and re-format it based on Leslie Lamport's "LaTeX: A document preparation System" (which is in my opinion still one of the best software documentations ever, worth a read alone because of that).
 Agreed, there's a great formula editor which is very nice if you want to create math presentations in powerpoint instead of in beamer (and I wouldn't blame you, especially if you're in a hurry).But could you really imagine writing a serious mathematical document (paper, book, thesis) in Word? No Git, no vim/emacs, no plain text? Abandoning the digital lingua franca of mathematical communication? Abandoning the packages written by the sum total of anyone who has worked on anything close to mathematics in recent years? For what?
 > But could you really imagine writing a serious mathematical document (paper, book, thesis) in Word?Yes I could, and I did. My Master's thesis is written in Word and it was pretty heavy on the theory and the formulas. If you're interested it's online on http://e.teeselink.nl/thesis_et.pdf. It's not a particularly stunning thesis in terms of content, but in my humble opinion it's a pretty document, definitely no worse than the average LaTeX-produced thesis.See eg page 58 (the 70th page of the PDF) for some large formulas. It's not arithmetic but Structured Operational Semantics, but I doubt that matters for this argument. (in hindsight I hate that page and the ones like it - the sheer overload of single-character variables makes it totally impossible to understand)By the way you said "no git" but Word files can be version controlled just fine - particularly when you're working solo which I was. I used Subversion (hey, 2007) but ok.I used Word because I noticed in earlier years that LaTeX made my mind drop down into "programmer mode" every time I wanted to accomplish something that was non-trivial. This nerd sniped me and it distracted me from writing the actual content. I ended up with super nice LaTeX themes and definitions and homecooked macros (excuse me for having forgotten the real names these things have in LaTeX, I last used it over 10 years ago), my content sources were super clean, but I spent at least as much time on setting up LaTeX as actually writing. Plus, I found editing large formulas frustrating because I had to find the right place in a fullscreen wall of backslashes and curlies.Word forced me to focus on the content because everything layout-wise I wanted to accomplish was boring and, mostly, easy.The only thing that was cumbersome was getting IEEE-style references (i.e. the ones that Bibtex generates by default) to work. It worked out in the end but wasn't as easy as it should be (I noticed that they fixed that since). Also I had zero problems with that thing where Word just doesn't want to do what you tell it to (indents jump, list items suddenly disappear etc, you know the drill) because I only used Word Styles (a bit like CSS classes) and never custom formatting. As long as you stick to that, Word sucks less.
 Frankly, this PDF shows that it has been produced with Word. For example: (a) Full justification without hyphenation; (b) Chapter 6 ends at page 69, and the next 32 pages have wrong left header; and (c) Section headers with fake small caps. Using LaTeX would have resulted in a more beautifully typeset paper.Your point that you might have spent more time preparing it is subjectively true, obviously, and it seems that in your case Word proved good enough.
 LaTeX uses a different strategy where WYSIWYG is no advantage. The markup commands tell the computer about the logical structure of the text. This is not possible in a WYSIWYG system precisely because it displays the final result, and intermixing both is a mess. Word is a glorified typewriter, LaTeX is a diligent professional typesetter.Apart from that: Microsoft Word /seems/ easy to use but this is not really true, by far. To typeset a minimal LaTeX document as for a homework assignment, very little learning and boilerplate is necessary. This can be done /quicker/ than in Word - an intelligent person will need half an afternoon to write a short presentable text in LaTeX, and the learned knowledge works forever. What you are assuming is that people are already used to write high-quality structured documents in Word, and this is, for most people, simply not true, as Words gets heavily in the way of writing in a structured approach. The ribbons UI has not really helped with that - I curse every time I have to search for a section formatting style in that terrible drop-down menu.Now when it comes to writing seriously complex larger text documents, like a large software documentation, a piece of literate programming, or a PhD thesis, MS Word is far far behind. It is simply not up to the task.You also say that Word has been getting better, but having occasionally been forced to work with Microsoft products in the last nine years, I really don't see that. The only thing that changes is the user interface. It is hardly believable that Microsoft will use office programs to try out new paradigms and software metaphors.And to add, I am also pissed by the appearance that Microsoft - not specifically for this comment, but very much in general - seems to follow the strategy to make their commercial products mentioned as much as possible in the context of free and open source software, in forums and in places such as reddit. There may indeed be a few people which use .NET or c# or the Linux subsystem or which give up the power of UNIX shells for an inferior solution, but I just can't get rid of the strong impression that the huge majority of such comments are just product marketing done by some PR company. It is annoying. And completely hollow. As here, somebody who really has medium knowledge on how to use LaTeX will rarely suggest to use Word instead.
 > You also say that Word has been getting betterI didn't say that. Like, not even close, where did you get that from? In fact I haven't noticed a single improvement in Word since 2007 except the installer.> And to add, I am also pissed by the appearance that Microsoft - not specifically for this comment, but very much in general - seems to follow the strategy to make their commercial products mentioned as much as possible in the context of free and open source software,I'm seriously bothered that you're accusing me of being a talking head for some multinational corporation. I'm a moderately happy customer, that's all. Our financial relationship is 12 euros a month, from me to them.If you really can't discuss the merits of software alternatives separately from some big "everybody who disagrees with me is on the enemy's payroll" conspiracy theory, the IMO you already lost the argument.> As here, somebody who really has medium knowledge on how to use LaTeX will rarely suggest to use Word instead.I used LaTeX in anger, then noticed that getting comfortably good at it doesn't make it a less shitty experience, and I decided that I preferred Word. Please note that I think that both Word and LaTeX are pieces of shit, I simply think that Word is slightly less shit (or, well, shit in a way that bothers me less and you're free to disagree).I think the fact that you can't imagine anyone knowledgeable could prefer Word over LaTeX shows a severe lack of empathy and imagination on your part.
 I wrote my dissertation and several papers for publication using mardown + pandoc + latex. On Arch. I have to say, you're far overstating the difficulty of this arrangement, and understating the benefits. As long as you're willing to accept the haskell package madness, which pacman takes care of for you, everything else works in a very straightforward manner. The trick is, you don't have pandoc generate straight through to PDF. You treat pandoc as a preprocessor, have it generate tex. Then your main LaTeX source file boils down to a bunch of \usepackages and \includes. I pulled it all together with a very simple makefile.The markdown source is a great deal more readable -- all of those little substitutions that seem inconsequential individually add up to a lot less noise in your document source. Equations just pass through to LaTeX, so you write them the same. All of my floats started out using markdown syntax, which is really beneficial when drafting, since much harder to mess up a single line when cutting and pasting it around. In the end, I wanted finer control over how they looked, so I pasted the generated tex into my sources and worked from there.My one caveat is, you absolutely must understand LaTeX first, or you will be in for a bad time. Pandoc + markdown + LaTeX is no substitute for understanding LaTeX, but it's a huge win if you're already familiar with LaTeX and you're tired of typing backslashes.Finally, the recommendation to use article is unfortunate. Memoir will save you a lot of headaches.
 > as long as you're willing to accept the haskell package madness
 I think it is worth the extra complexity to avoid having to write \section and \emph all the time, and to make your notes more readable as a .TXT files. Also I find it easier to just set up a basic document, for markdown you can just open a new text file and start writing, for Latex you have to do a lot of setup at the start of the document to define your margins and import packages. Its not going to work well if you want a perfectly formatted document, but if you want to write simple notes styled with CSS it is much nicer to work with.
 Pandoc is awesome for things like tables or code blocks.Here is a table in pandoc markdown: | Header 1 | header 2 | |-|-| | Column 1 | Column 2 |  Which is easy to write via emacs mode/vim plugin. Similar for code blocks. Plus this is extendable, I frequently use an extension that transforms DOT syntax into embedded graphs.
 Tables are very complicated in LaTeX... but for a goodreason: tables are just hard. In your example:- Should the table appear flushed to the left? Centered in the page? flushed to the right? Full-width or only content-width?- What happens when Column 1 is long? Should the text wrap inside its own cell, overflow, or what?- Which row/column lines should appear? None? All of them? Only those that separate headers?These matters will only get more complicated once the table starts growing.Of course, you could say that all these issues are presentational, and hence it's your theme's job to handle, not yours. That is fine until it breaks and you need to fix it though...Code blocks are very easy in latex too. Install the "minted" [1] package and you can just: \begin{minted}[python] def something(): ... \end{minted}  About extensions, it depends I suppose. In your case I would use some rendering app like graphviz and just \includegraphics the resulting ps/pdf. All this can be easily scripted (if you are able to create an extension you should have no problem writing a script that rebuilds your ps/pdf files before building the latex file).I do think that writing simple files in markdown feels better than doing it LaTeX. Unfortunately, as the document starts getting more complicated it's always been easier for me to just turn to "pure" LaTeX than to try and deal with it through pandoc extensions.
 I think the author mentioned this elseware, but he wasn't suggesting to use .md for complicated documents, just for notes and simpler documents where you don't need the extra options like complex table formatting, you just want something quick that works.
 Thing is, if you're already looking to use e.g., Emacs, you'll be better off using org-mode instead of markdown. Same lightness of syntax, tens of times the functionality (including much better tables, which you can use directly from a TeX document, as well, via radio tables).Editing ascii tables with no editor support is painful.There's also some org functionality in vim plugins, though I've never used them, so I don't know how much they cover.
 > if you're already looking to use e.g., Emacs, you'll be better off using org-modeI find that you should use org only if you use Emacs. Vim plugins for Org are very limited, and this is even more true for other editors.Judging a technology only for its technical merits is unproductive. Markdown has "won", it's everywhere and everyone can learn to use it. Those are damn powerful advantages.Using Markdown, I gain the ability to read and write on a smartphone or tablet in my phone or tablet, which for some notes is extremely convenient. Many times being able to access my notes on philosophy from my phone during a bus commute allowed me to develop and write down a thought, which would have been a pain to do with other technologies. Of course I could have done the same with other options, but this ubiquitous convenience and effortlessness is great.What I'd love to see is a way to transition easy-to-write-everywhere to more powerful type-setting easily when needed. May be combining Markdown and Latex? Or converting Markdown to Latex before publishing?I'm sure this exists already; I just haven't needed it enough yet :)
 I don't doubt that using org outside Emacs may be problematic to some degree (in terms of expected functionalities, anyway), but I use Emacs for everything, so it's not really an issue.If popularity alone were sufficient for technological choices, we wouldn't even be having this discussion (and we'd all be using Windows). I try to choose my tools according to how well they work for me. Markdown, in my opinion, is a poor choice compared to org, but I can use it to collaborate with others, no problem.As for the transition from light markup to TeX, that's pretty much the point of the OP, isn't it? Maybe the break point is different for everybody. For me, LaTeX imposes no extra cognitive load, but then again, I've been using it extensively for many years. If I'm need for something lighter, it'll be org (but really, org usually wins for me because of how well it does all the other stuff, not just the markup part).
 I’ll second this. We’ve had good experiences converting org-mode files to LaTeX for internal documents.
 It might surprise you, but lots of documents and side sets are written without any formula at all.
 But arch has pandoc in pacman. All you have to do is pacman -S pandoc
 Right, but look at its dependencies. Arch links haskell packages dynamically, so you easily end up in DLL hell.
 Yes it links them dynamically. Why is that a problem? How would that end in DLL Hell? (which is multiple versions of dlls around and different pieces of application using different versions at same time in same process and never being sure what is using what)
 I do reach for Markdown/Pandoc whenever possible, but on longer documents one will end up using lots of LaTeX tricks to get the job done (newcommands, subfigures, or that strange package that respects the typesetting conventions of your field).Plus, I think Pandoc-based collaboration is still out of reach, as there are simply too many moving parts: the underlying LaTeX distribution, templates, filters, most of them only available through cloning git repositories.So a typical workflow of mine is: draft in Markdown/Pandoc, start adding stuff, but migrate to LaTeX very soon if you notice something is going wrong (also, the Pandoc LaTeX output sometimes needs some tweaking, so it's better to leave Markdown while the document is relatively small).
 For simple stuff, I prefer org-mode. I have great memories of using OmniOutliner on OS X Tiger. The hierarchical nature of outliners is great for structuring thoughts quickly. Org is even better, as it's plain text and has tons of modules for all sorts of crazy things, including kanban or spaced-repetition. And plenty of export options, including many facilitated by pandoc, literate programming, etc.I do use LaTeX, but I have a love-hate relationship with it. Lots of LaTeX packages don't compose well, and there are tons of pitfalls. But there are beautiful parts too, like TikZ or Memoir. I'd be happier with TeX, but few people use that.
 We recently added support for embedding LaTeX expressions (and really, any dynamically-generated DOM) within Markdown template literals to Observable notebooks. So you can say mdI like {tex\\KaTeX}, and KaTeX renders its logo, which is then embedded within the generated Markdown.I’m admittedly biased, but I love the ease of writing Markdown combined with being able to inline arbitrary DOM for math, sparklines etc. More examples here:https://beta.observablehq.com/@mbostock/measuring-color-diff...  Mike, great job on Observable and thanks for all your work on D3 as well! I read through the whole thread about observable that was on hacker news a couple weeks ago, but I didn't see an answer to a question I have. Are there any plans to allow observable to be run locally like a jupyter notebook? Like an app or anything. Even if the site was like a progressive web app that could be nice.I know observable as a whole is not open-source so I understand this may not align with the best interests of the company. Also observable is fairly new so I'm sure you have a lot higher priority features on the release radar. I honestly wouldn't mind paying for an application even if it was an electron app.Anyways good luck with Observable! I think its a great notebook format with a great API.  I worked around the inline math issue by doing: md2 = x => md([x[0].replace(/\(.*?)\$/g, m => tex([m.slice(1,-1)]).outerHTML)])  I do appreciate you adding support for${tex...}, but it's still a bit more verbose than I'd like to type.
 Well, it’s nice that you can always define your own tagged template literal. ;) The double backslashes certainly are annoying. We may be able to eliminate them by using String.raw. https://github.com/observablehq/notebook-stdlib/issues/10
 I just saw that pop up on the front page of observablehq. That resolves another pain point for me. (My first experiment with the platform happened to have a lot of math exposition in it.)
 I don't think most people are reaching for LaTeX to write to-do lists or other ephemeral notes (which can be pretty effectively written just in .txt), but because they'll need some feature that is simple in LaTeX but difficult or impossible elsewhere.However, I doubt anyone who argue with a modified premise of "Reach for Markdown, not LaTeX, when writing blog posts." But that wouldn't produce as many clicks, either.
 Is that not what it says? The last sentence of the first paragraph is "By reaching first for Markdown, then for LaTeX when necessary, writing is easier and more enjoyable", which would be that premise but applied to any situation where LaTeX is overdoing things.
 I used LaTeX all the time at university. It made citation/bib easy, it made writing reports for mathematics way more efficient, and the presentation of the documents were beautiful. I had a prof rave about how nice the my paper looked once when I turned it in.I wish I had stuck with it afterward. I write enough that it would make my work less painful, but I let the skill laps. This article is making me think I should pick it back up.
 I really wish I had bitten the bullet and learned LaTeX in college. At the time, trying to actually write a research paper start-to-finish in Word was too painful, too prone to crash and lose data, and badly incompatible with using version control (CVS and SVN, at the time), and so I settled on a process where I'd write the whole thing in plain-text, and insert my citations in inline parentheses, then when I was all done, have to go back and try to format the thing in Word with proper footnotes and formatting. More than a few times, it took nearly as long to get that post-processing right for printing than it did to actually write the paper.
 I'm not in a science department; we have hard requirements to hand in Word documents at times. It hurts my soul.
 I find many of these points unconvincing. All of the pros listed at the beginning also apply to TeX, some arguably better than to Markdown. As far as I can tell, Markdown has several advantages over LaTeX, but these aren't highlighted in the article:* Markdown is easier to learn (at least the basics)* Markdown is more readable when in plain text format* Markdown doesn't require boilerplate/metacode such as package imports* Markdown more easily and naturally renders to HTML (biggest one in my opinion)(I don't particularly find any of these that convincing for my uses except maybe the last one.)
 Given how easy the markdown specs are, it is unbelievable how different the text is rendered using different engines.
 The text is rendered with CSS, so you should be able to specify whatever rendering style you want using something like Pandoc.
 Really appreciate this piece. I have been doing more rmarkdown into pdf through pandoc/latex/etc. (yea its complicated but made much easy by the R community) for my English resume editing business. Still wading into Latex to customize docs feels like hieroglyphics. Seems made for grad students with too much time on their hands. The learning curve is steeper than I want or need to to be as an intermediate tool.Addendum: I would really recommend crowd here look at rmarkdown flavored work. There are now a ton of community offerings for resumes/CV/theses even academic journal article templates. Most can be found on github.com and CRAN (the central repository for non-base packages).
 RestructuredText has generally worked nicer for me that Markdown. Especially when combined with Sphinx you can easily embed LaTeX math structures as well.Having that said, depending on the scale of the paper I usually tend to go back and forth between RestructuredText and LaTeX. When it's large and might need some fine tuning it's better to use LaTeX, when you simply need to jot something down... no need for the complex LaTeX setup.
 > RestructuredText has generally worked nicer for me that MarkdownAgree. As soon as you want to start having references to other parts of your document(s) RestructuredText wins out over Markdown.
 Using Typora for WYSIWYG markdown editing using inline LaTeX and a LaTeX-like theme (http://theme.typora.io/theme/Academic/) has been a nice middle-ground for my most common use-cases of homework and notes. Full LaTeX is wonderful but feels like overkill in many situations.
 LaTeX for scientific documents, Markdown for lightweight text documents, and ODT from a text editor for everything else.
 Reach for emacs org mode, then export to whatever and if you really have to use pandoc.
 If you are just reaching for something to jot notes and whatnot, you could do worse than looking at org mode. Pandoc is nice, but I have yet to find that a simple export from org doesn't get me most of where I want to go.
 For an intermediate choice, I would recommend AsciiDoc [http://asciidoc.org/]. I currently use it for some of the more complicated pages on my company's GitHub wiki, and am very satisfied with it.For an example of its usage and look, here [http://asciidoc.org/INSTALL.txt] is the source from which this [http://asciidoc.org/INSTALL.html] page was rendered.
 When I prepared my master thesis some years ago, I needed to extract parts of the main materials to build another small book that contained only the main ideas, theorems and proof highlights. \LaTeX and it's programming interface really helped as I could define a new environment for example\begin{shipboth} contents for both thesis and the small book \end{shipboth}This is an example of making things DRY. How can I do the same with Markdown (and their tools)?(Well I rarely use \LaTex today; my R\'esum\'e was typeset in \LaTeX and it helped me to get a good job but when it has so many things I just write them in a .odt file)
 I found Markdown quite lacking for things like documentation. Restructured Text with Sphinx was similar to Markdown in usage but significantly more flexible (especially references other parts of the documentation).
 Pandoc is really awesome. Even mathematics papers can be written in (mostly) markdown, and then converted to latex before compiling to PDF.For mathematics I would also recommend using Unicode symbols in place of LaTeX commands, which makes the source even more readable. For instance$∏_{x∈X} ∑_{y∈Y} Ψ(x,y) → ∑_{f : X → Y} ∏_{x∈Y} Ψ(x,y)$instead of$\prod_{x \in X} \sum_{y \in Y} \Psi(x,y) \to \sum_{f : X \to Y} \prod_{x \in Y} \Psi(x,y)$To get this compiling, your template will have to include declarations for these such as:\DeclareUnicodeCharacter{220F}{\ensuremath{\prod}}
 You can avoid having to declare each character separately if you use the unicode-math package: https://github.com/wspr/unicode-math . I suggest you try it; it's life-changing for e.g. general relativity stuff where there are a lot of Greek letters being thrown around!
 That looks really interesting! Thanks for sharing!
 But you can type the second one way easier
 Not really! I use an XCompose file derived from the Plan 9 keyboard setup. So to write ∏ i press my modifer (left shift) button once, and then 'p' followed by 'r'. So it is fewer key presses than \prod (three key presses vs five).I have similar shortcuts for all maths symbols I use regularly. Here is an excerp from the configuration2200 fa ∀ for all2202 pd ∂ partial differential2203 te ∃ there exists2205 es ∅ empty set2206 De ∆ increment2207 gr ∇ nabla2208 mo ∈ element of(…)220E qed ∎ tombstoneThe last one is most sattisfying to type !
 Not necessarily -- with the right editor, e.g. Emacs, you can have it automatically convert "\alpha" to "α" (built-in TeX input mode), or if you're using AUCTeX, you can type "a", which would be easier than "\alpha" or "α"!Edit: Oops, saw the sibling post. That also works, although sadly I can't take always advantage of that since I'm not always on Linux.
 There's a very simple emacs extension called "pretty lambda", which displays a word "lambda" as a lambda character (but presents as ascii still). I wonder if something like this is possible to do here (of course, the syntax with arguments makes it harder).
 Using XCompose (see sibling post) has the advantage of working in all programs on X, and producing real unicode.
 I would like to see somebody write their PhD thesis in markdown.
 I did! My maths phd thesis was written in markdown.
 I wrote my MSc dissertation in Markdown
 I agree. Had started a project aiming to translate various literature books (no fancy math) into various languages, and markdown makes it a lot easier, for everyone. http://github.com/ancap-ch/from-enBut it's required some regex "replace_all" to be applied when rendering the PDF.
 This reminds me very much of the emacs org-mode experience. But the good (bad?) thing about this is that it doesn't require emacs. I was looking for an alternative to recommend to my friends, since having to learn both the new notation and emacs really creates some friction.
 This is why I reach for Org mode.
 I imagine many people are already using Latex inside Markdown, a rather nice solution for the quick production of mathematical texts.
 Use both. RMarkdown + Beamer or something.