-PostScript: Not actually widely used now, but PDF is basically the same thing.
-PDF: A way for adobe to make money
-SVG: Based on the DOM model, vector format
-BMP,PNG,GIF: Are these even worth mentioning?
+\subsection{Blurring the Line --- Javascript}
+
+\begin{itemize}
+ \item The document is expressed in DOM format using XML/HTML/SVG
+ \item A Javascript program is run which can modify the DOM
+ \item At a high level this may be simply changing attributes of elements dynamically
+ \item For low level control there is canvas2D and even WebGL which gives direct access to OpenGL functions
+ \item Javascript can be used to make a HTML/SVG interactive
+ \begin{itemize}
+ \item Overlooking the fact that the SVG standard already allows for interactive elements...
+ \end{itemize}
+ \item Javascript is now becoming used even in desktop environments and programs (Windows 8, GNOME 3, Cinnamon, Game Maker Studio) ({\bf shudder})
+ \item There are also a range of papers about including Javascript in PDF ``Pixels or Perish'' being the only one we have actually read\cite{hayes2012pixels}
+ \begin{itemize}
+ \item I have no idea how this works; PDF is based on PostScript... it seems very circular to be using a programming language to modify a document that is modelled on being a (non turing complete) program
+ \item This is yet more proof that people will converge towards solutions that ``work'' rather than those that are optimal or elegant
+ \item I guess it's too much effort to make HTML look like PDF (or vice versa) so we could phase one out
+ \end{itemize}
+\end{itemize}
+
+\subsection{Why do we still use static PDFs}
+
+Despite their limitations, we still use static, boring old PDFs. Particularly in scientific communication.
+\begin{itemize}
+ \item They are portable; you can write an amazing document in Mathematica/Matlab but it
+ \item Scientific journals would need to adapt to other formats and this is not worth the effort
+ \item No network connection is required to view a PDF (although DRM might change this?)
+ \item All rescources are stored in a single file; a website is stored accross many seperate files (call this a ``distributed'' document format?)
+ \item You can create PDFs easily using desktop processing WYSIWYG editors; WYSIWYG editors for web based documents are worthless due to the more complex content
+ \item Until Javascript becomes part of the PDF standard, including Javascript in PDF documents will not become widespread
+ \item Once you complicate a PDF by adding Javascript, it becomes more complicated to create; it is simply easier to use a series of static figures than to embed a shader in your document. Even for people that know WebGL.
+\end{itemize}