It's a problem and yes we plan to fix it. I'm sorry it hasn't been fixed yet; we're just slow at things. Hopefully HN will be around for long enough to justify how slow we are.
That's great news and thanks for the swift reply. Have you considered asking the HN community for help with this issue? I'm sure there would be lots of volunteers.
My wish list is not full Markdown support, but a little more than is currently implemented:
1. Ordered lists
- Unordered lists
Inline `code snippets`
Super^script
That's it. I totally get why HN wouldn't want tables, bold headers, etc. There's a danger of comments getting visually "noisy" with these. But for referencing code or mathematical concepts, or just listing things, the 4 things above would be really handy.
I find I can make unordered lists quite effectively
• like this
• using characters like
• U+2022 BULLET
‣ Or U+2023 TRIANGULAR BULLET
Similarly, you can do superˢᶜʳⁱᵖᵗ using Unicode as well (though I would only recommend it for numbers; Unicode doesn’t include all superscript letters, and most of the ones it does include look bad when used together). But yes, I agree that proper support for these things would be very good. (Especially code blocks!)
Yeah, I’ve done it before for superscript characters and even have used fixed width code points to force inline code. But it was cumbersome. (One time my whole comment was written in fixed width characters—I don’t remember why—and I found it a few hours later transliterated to the 0-127 range)
EDIT: Also, with native list support, you don’t get the wide line spacing. I like lists that aren’t paragraphs for each item.
Yup... Lists, `inline`, and ```code``` would be fantastic. It's so annoying for n.yc to be literally the only place on the internet where you can type into a textbox but that textbox isn't some variation of markdown. (even facebook messages [on web] supports triple-ticks for code!)
I work at Vanilla Forums (we power some of the largest communities online).
I’ve worked a lot on our editors and content formatting pipelines. We support plaintext, markdown, HTML, BBCode, and a WYSIWYG editor with markdown shortcuts.
In reality is estimate the distribution is mostly the WYSIWYG editor nowadays for newer sites and BBCode for the older ones (some users on older entrenched communities really like their BBCode I guess).
True, but it's such a mismatch in expectations where the entire tech industry has embraced markdown, but n.yc (tech mecca / water cooler) is most decidedly (and surprisingly) uses NotMarkdown(tm).
