undefined | Better HN

0 pointsdaviross10y ago0 comments

This has been my current approach for a while, after exporting everything out of Tiddlywiki when it looked like that was dying for a while (Browser support drying up, etc).

Now that it's been revived with Tiddlywiki5 and development's picked back up, I'm somewhat tempted to get back into it. Main advantage: Better crosslinking, rich content, etc. Main disadvantage: Less simple to edit, some tedium to export.

I'd love to have a Tiddlywiki-like frontend to a set of Markdown text documents backing it. (This is something that's been gnawing at the back of my mind long enough that I might have to buckle down and make it myself) Maybe Markdown + JSON for rich content data...

0 comments

3 comments · 1 top-level

dheera10y ago· 2 in thread

Where I need markup, I've been sticking to HTML or LaTeX syntax for the most part.

Partly because I hate Markdown due to its inconsistent syntax (that's my personal opinion), but also because it feels like a fad of recent years, much like a successor of the MediaWiki fad and the BBcode fad. I feel like in another 2 or 3 years someone will invent Markleft or Markright or Visual Markdown#.NET 2.0 or Dustindown that's 10 times better than Markdown, and then I'll have to switch everything over yet again.

HTML and LaTeX on the other hand, aren't dying any time soon due to their extensive deployment, and I'm confident that my syntax will be renderable for at least another 10 years or more.

ta096710y ago

i'm not sure you'd consider it better markdown (i do), but do you know about reStructuredText? it seems to even predate markdown. http://docutils.sourceforge.net/docs/user/rst/quickstart.htm...

hammerandtongs10y ago

Emacs and orgmode are probably your next step :)

orgmode is really a superset of markdown with PIM markup added.

It exports to markdown and a ton of other formats.

Cheers.

j / k navigate · click thread line to collapse