emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Peter Neilson" <neilson@windstream.net>
To: emacs-orgmode@gnu.org
Subject: Re: Efficiency of Org v. LaTeX v. Word
Date: Sat, 27 Dec 2014 04:06:03 -0500	[thread overview]
Message-ID: <op.xrirkdcirns8nc@odin> (raw)
In-Reply-To: <87sig1d8ee.fsf@pierrot.dokosmarshall.org>

On Fri, 26 Dec 2014 23:27:37 -0500, Nick Dokos <ndokos@gmail.com> wrote:

> Anyway, color me deeply suspicious of the "study".

Indeed!

The study touches only a few of the inherent difficulties in document  
production. Its major flaw is that it draws any conclusions at all  
recommending that authors produce documents one way or another. Personally  
I am always disappointed when someone requests a document in MS Word  
format, because that means I'll have to fire up Libre Office and shove my  
text through it, rather than using whatever other system I happen to have  
been using. I do not believe that I currently own a system with genuine MS  
Word.

As well as having insufficient control of variables, and a flawed  
understanding of what is involved in "document preparation," the study  
also has a marginally small sample size. Any study for any purpose that  
presents "statistics" with sample sizes smaller than 30 is immediately  
suspect. I won't even begin to address the misinterpretation of  
correlation as causation that appears in the "softer" sciences, nor their  
necessity for sample sizes far larger than 100, nor the tendency in some  
fields to mistake a time series as a set of samples.

MS Word works extremely well for "one-off" small papers. Little investment  
of effort is required for a naive person to produce adequate results, and  
as every user of emacs knows, that's pretty much the opposite of emacs.

On the other hand, MS Word has historically been a terrible tool for  
producing large documents, or documents that are to be maintained by a  
group of people, or over several years or decades. Handling Word's "Master  
Document" provision without being crippled by corrupted documents is an  
art form unto itself. The standard advice among experienced users of Word  
has always been, "Don't Use Master Documents!" When a group of people are  
all editing versions of a document, any attempt to use standard formatting  
in Word requires substantial effort to prevent naive contributers from  
reformatting outside the established styles, or even breaking all the  
styles. Furthermore, Word documents are in general not amenable to  
incremental version control as commonly used by coding teams.

My conclusions? If your paper is trivial and you are under pressure to  
produce it quickly, then MS Word might be the best tool. Established  
journals should attempt to allow contributions in more than one format,  
and restriction to MS Word format is a bad idea, no matter how much some  
people like the apparent ease-of-use that MS Word provides. Attempting to  
extend the "study" to include org mode would be a waste of effort.

  reply	other threads:[~2014-12-27  9:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26 22:47 Efficiency of Org v. LaTeX v. Word Ken Mankoff
2014-12-26 23:36 ` Thomas S. Dye
2014-12-27  2:21   ` briangpowell .
2014-12-27 14:36     ` Eric S Fraga
2014-12-27  3:26 ` Christopher W. Ryan
2014-12-28 22:45   ` Bob Newell
2014-12-27  4:27 ` Nick Dokos
2014-12-27  9:06   ` Peter Neilson [this message]
2014-12-27 14:38     ` Eric S Fraga
2014-12-27  9:48 ` Achim Gratz
2014-12-27 10:05 ` Paul Rudin
2014-12-27 10:36   ` M
2014-12-27 11:36     ` Fabrice Popineau
2014-12-28 22:43       ` Pascal Fleury
2014-12-31 18:19     ` Paul Rudin
2014-12-27 13:37 ` Daniele Pizzolli
2014-12-28 21:40 ` Efficiency of Org v. LaTeX v. Word ---LOOK AT THE DATA! Christophe Pouzat
2014-12-29 19:47   ` Thomas S. Dye
2014-12-31 16:59   ` Colin Baxter
2015-01-04 20:38 ` Efficiency of Org v. LaTeX v. Word John Kitchin
2015-01-04 21:15   ` Andreas Leha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=op.xrirkdcirns8nc@odin \
    --to=neilson@windstream.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).