I've started thinking of TeX as the assembly language of document formatting, LaTeX as C, and org-mode as... pick your favorite higher-level language here, I'll go with Python.
Not a perfect metaphor, but in terms of paper productivity it feels that way.
> I've started thinking of TeX as the assembly language of document formatting
I remember having read a Knuth interview saying exactly that's what he intended TeX to be. He was also surprised that everyone settled for LaTeX instead of creating their own TeX dialect designed specifically for their own needs. > Not perfect, but I find it's more natural to write in org-mode
Do you have any specifics on the problems you faced? I produced my master thesis entirely using orgmode without any problem. (defined custom latex class, with different kind of ToC etc, not that difficult)Org-mode is great for structural editing and tables, and simplifies some aspects of LaTeX (images, for sure). I still find myself "dropping down" into LaTeX. I don't think it's an inherent weakness in org-mode, it's just that now I keep track of org-mode and LaTeX commands.
Additionally, Markdown is far less threatening to technophobe collaborators. I've successfully written grant applications with clinicians using Markdown in an etherpad document (free hosted version at http://piratepad.net/), which I later converted to LaTeX/pdf for submission. They would never have put up with writing lists or headings in straight LaTeX.
EDIT:I should have stated that pandoc is a nice tool for conversion between a bunch of formats including Markdown, Latex, Html, s5, reST, RTF, epub and a few others. In response to the comments below about conversion to word always sucking, pandoc provides the least sucky attempt I've found so far.
I did use LaTeX to take notes all through college and it has certainly helped ingrain it well into my muscle memory.
http://orgmode.org/manual/LaTeX_002fPDF-export-commands.html
It could be done another way, but in the era that TeX was developed, it would have required more memory than was realistically available most of the time. I find that once I've run it twice, I can get away with single runs usually after that until I'm ready for the "definitive" version. Until then, I'm less concerned with whether the cross-reference is right, than whether there is a cross-reference in that location at all.
Another gcc analogy is a dependence on a third-party library whose API keeps changing. Then you'd have to run gcc once to regenerate the library, and once on the client using the library.
Peeling that back a level, the analogy is between files like libfoo.a and foo_defs.h (for gcc) and files like section1.aux and document.bbl (for latex).
I use the following Makefile wrapper around it:
DOC = memoria
all:
rubber --pdf $(DOC)
clean:
rubber --pdf --clean $(DOC)
.PHONY: all clean
It handles biblography, knows how many times recompile and discovers dependencies.This is what I've been using, inherited from a colleague/committee member/friend:
PAPER = paper_name
SECTIONS = $(PAPER) abstract introduction design results conclusions
default: $(PAPER).pdf
$(PAPER).bbl: $(PAPER).bib
pdflatex $(PAPER).tex
bibtex $(PAPER)
$(PAPER).pdf: $(PAPER).bbl $(foreach SECTION,$(SECTIONS),$(SECTION).tex)
pdflatex $(PAPER).tex
pdflatex $(PAPER).tex
pdflatex $(PAPER).tex
clean:
-rm -f *~
-rm -f $(PAPER).aux $(PAPER).log $(PAPER).out $(PAPER).bbl $(PAPER).blg
-rm -f $(PAPER).idx $(PAPER).ilg $(PAPER).ind $(PAPER).dvi $(PAPER).toc
-rm -f $(PAPER).pdfMy buddy during my undergrad used LaTeX, at the time the thought of debugging my documents seemed insane (though he could do some amazing ninja stuff like rebuilding his graphs in matlab and importing them on build). Since starting my masters, I've taken it up, and yes it is awesome.
On the other hand, it does support currying of macros!
My main TeX annoyance is tables, but I don't think anyone has come up with a decent way of expressing them in a textual manner.
On the sucky side, the toolchain is notoriously difficult and cryptic. For some reason you have to make multiple passes of various tools by hand (or with a makefile -- i reccommend http://code.google.com/p/latex-makefile/ it just works). The syntax can be a bit inconsistent. The worst is the errors tho, sometimes it is impossible to figure out why all your figures are showing up at the end of the document instead of in-place, or why all your references are failing to point at anything.
Overall tho, it is a fantastic system :)