Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • This is very close to the philosophy behind something I've been building:

    https://github.com/simonschnake/Mark2Tex

    I built Mark2TeX while writing my thesis in Obsidian. I wanted to write the prose in Markdown, but keep a normal LuaLaTeX document for math, citations, cross-references, etc.

    So Mark2TeX lets me use Markdown-like files and drop into real LaTeX whenever I need it.

    I deliberately didn't try to build a complete Markdown/Pandoc replacement. It's basically an attempt to under-engineer the Markdown/LaTeX boundary.

  • As an aside, timelapse videos like this are a useful proof of thoughtfulness in the age of AI slop
  • And here I've just been using pen/paper for outlining and notes and then GoogleDocs for mine.
  • Why not Markdown - pandoc - epub/pdf?
  • I finished a BSc and an MSc with quarto and fossil. It had to be in Word so I wrote a VBA script that pulled comments so I could edit my markdown files easier.
  • Is there a word for the right amount of engineering? Kind of a negative concept of not engaging in performative conceptualization. Just doing it in a way that the implementation was natural and not worth writing home about.
  • The related Over Engineering Post - https://news.ycombinator.com/item?id=49335292

    Does seem like overkill but everyone scratches their own itch.

Explore Birbla archives