TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Why You Shouldn’t Use “Markdown” for Documentation (2016)

3 点作者 _xivi超过 1 年前

1 comment

alpaca128超过 1 年前
The inconsistencies between Markdown implementations are annoying, but in my experience it&#x27;s rarely an actual problem. Most seem to aim for Github&#x27;s flavor with maybe one or two deviations, which seems to be the closest Markdown ever had to a standard. Whenever I try a note-taking or messaging app I just go in with that assumption and it usually just works.<p>Also let&#x27;s not pretend other formats have necessarily more consistent or complete implementations. Sure, Github supports 9 different markup formats, but go try using .org files in anything but Emacs and you will always be disappointed. Some implementations can&#x27;t even render checkboxes and pandoc is very inconsistent as well, not to mention a complete implementation would also need to fully support LaTeX.<p>&gt; for any reasonably sized set of docs you’ll need things that aren’t in the basic language.<p>Any examples of features that aren&#x27;t supported by Github Markdown?<p>&gt; With other markup languages, you can extend the language to provide the features that you need.<p>Markdown can be mixed with HTML. Not ideal but very flexible.
评论 #37788814 未加载
评论 #37788548 未加载
评论 #37788690 未加载