Show HN: Mathematics Chalkboard with LaTeX and Markdown Support
github.com
github.com
\section{title}
and # title
If this is the only "advantage" of Markdown with respect to LaTeX it seems quite feeble...
Is there anything else of substance that the Markdown+LaTeX mix allows?Markdown is easier to use. Markdown extentions like Rmarkdown (Inc. R Notebooks) are a pleasure to use.
TeX is a a turing-complete language, picking some random subset of LaTeX commands would feel pretty arbitrary to me. In comparison, supporting full markdown syntax is pretty easy.
Yes. The publishers are in business for their readers, not their authors, even though those audiences often overlap. If putting a hardship on their authors will help their readers, even in a notional sense—"because of the restrictions we put on TeX documents, the people we need to hire to deal with TeX only have to have basic skills, and so we are better able to concentrate resources elsewhere in the workflow"—then they will. (I'm not defending this choice, just reporting on it. A recent dealing with IMRN made it horrifyingly clear how little their TeXnical staff understands about the most basic TeX.)
> Being Turing-complete doesn't mean being an attack vector: when reasonably sandboxed, the LaTeX code is still confined to producing an output document, not exfiltrating your secret data or holding you to ransom.
Everything is an attack vector, and Turing complete things are even more so. Plenty of people have thought that they have reasonably sandboxed things and found out later that they hadn't. TeX is an incredibly reliable piece of software, and I'm sure great strides have been made in making it also a secure piece of software, but the security features have received much less battle testing and so should be trusted less.
I'm not sure why Turing completeness makes it easier or harder to choose a subset—perhaps easier, since "make it not Turing complete" should be a guiding principle for anything you compile on behalf of someone else—but MathJax and KaTeX are both pretty good guides for an "acceptable" subset.
I'm now fast enough that I'm able to just take notes in LaTeX directly, but for that first little while, Markdown was a very useful backup.
The other benefit was that Markdown is so easily extensible. I wrote a very small little DSL for expressing graphs, and then had the generator render anything in certain code blocks as a Cytoscape graph which I could interact with in the output pages. Wouldn't even want to try adding that to LaTeX.
Never underestimate the importance of a thin layer of familiar syntax for easing adoption!
Fair enough. Similarly, the "familiar" GUI interaction paradigm that Outlook Web Access forces on me (to pick an example that's on my mind as I am struggling with it) is much less convenient and familiar to me than a text-based interface as I'd get with Pine. However, we get what is (thought to be) familiar and comfortable to the intended audience, and we might not be the intended audience for the software that we want to use.
No it doesn't.