3 ms·
The first paragraph of https://daringfireball.net/projects/markdown/ https://daringfireball.net/projects/markdown/: “Markdown is a text-to-HTML conversion tool
by Someone 5y ago
The first paragraph of https://daringfireball.net/projects/markdown/ https://daringfireball.net/projects/markdown/:
“Markdown is a text-to-HTML conversion tool for web writers. Markdown allows you to write using an easy-to-read, easy-to-write plain text format, then convert it to structurally valid XHTML (or HTML).”
⇒ I think “easy to read and write” is an important, but secondary goal. The goal is to render to (X)HTML.
That’s similar to how SwiftUI’s
struct ContentView: View {
var body: some View {
Text("Hello World")
}
}
is deemed an improvement over, for example, Java Swing’s
JFrame frame = …
JLabel label = new JLabel("Hello World");
frame.getContentPane().add(label);
but in both cases, it’s the result that counts.
- deleted 5y ago[deleted]
- zamadatix 5y agoFrom your same link it does not say un-rendered readability was a secondary goal, it says the exact opposite: > The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. This also fits with the ordering from the second paragraph: > Thus, “Markdown” is two things: (1) a plain text formatting syntax; and (2) a software tool, written in Perl, that converts the plain text formatting to HTML. Markdown has always included rendering capability as a goal but I think GP is right, Markdown was never intended to be an always render first format just because it included the capability to render.