The problem with Org mode

I know that my ideas in this article will be hated by many staunch Org mode supporters. I still believe I am right.

For the last few years I have been using the Emacs plugin Org mode. This is an amazing text outliner tool that can do just about anything. As a student I used it to create Latex document, Latex Beamers, project websites etc. Its coolness knows no bounds, you can even create a spreadsheet in plain text!

Despite it being such an amazing tool, Org mode has some serious problems:

It does not use Markdown syntax.

Ok, so this is probably not really a valid point, since Org mode predates Markdown. Unfortunately, today, Markdown is everywhere. A lot of people know the syntax and are writing tools supporting the syntax.

For almost 3 years I was a loyal Org mode supporter, opting to use Org mode instead of Markdown syntax whenever possible:

The problem with writing Org mode README’s is that it makes collaboration difficult with people that know only Markdown. Github is also the only site I know of that will even render Org mode online. (Bitbucket, for example, doesn’t)

The problem with my Jekyll plugin is that it increases the complexity of publishing to Github Pages. Github, for obvious reasons, do not allow custom plugins in their build. This means that if you want to use my plugin you need to build the site locally, and then commit the HTML to master. You probably also want to commit the source somewhere, so you create a different branch and commit it there.

If you use Markdown syntax however, Github will build the HTML from the source directly. You just commit your source to master and Github takes care of the rest.

It is too tightly integrated with Emacs

Another problem with Org mode is that it is so tightly integrated with Emacs. My major issue with this is that it prohibits collaboration. I cannot simply give my Org mode source to a non Emacs using friend and explain to them what to install, and what command to run in order to compile it. I would first need to give them about a six months worth of Emacs lessons for them to be able to use it.

The answer

About a month ago I got tired of swimming upstream, and started embracing Markdown instead of Org mode wherever possible. So far this has been a liberating experience.

If I was the Org mode author, I would look for a way to switch to Markdown syntax, Org mode flavored Markdown if you like. I would keep the Org mode features that Markdown lack, like tables. You could maintain a ‘legacy mode’ for old Org mode styled documents.

I would also extract as much of the Org mode core as possible from Emacs lisp code. I would rewrite it into a modern programming language. (Python or Javascript seem like obvious choices) This would give me the possibility of more collaborators getting involved. I would then write Org mode plugins for Emacs, and one other editor (Vim or Atom).

Org mode is a great tool. It has the potential to revolutionize the way we do text editing, but it needs revolutionary thinking to get it there.

Projects · Blog · Gallery · About ·