The writeup does not mention Jeff Atwood (Stackoverflow founder) trying to convince Gruber to standardize markdown. Atwood approached him publicly in a series of blog posts, but Gruber kept silent, and if I remember correctly finally declined stating that he didn't want to spend time jumping through other persons' hoops. Although it sucks that markdown is not standardized, I still see this as an inspiring example of…
How Markdown took over the world
251–260 of 353 posts
Re: How Markdown took over the world
#252Earlier quoted context omitted.
“Markdown” is a family of writing formats. There is no one “Markdown”. It’s completely unsuitable for direct inclusion in the web platform. Related reading: https://www.rfc-editor.org/rfc/rfc7763.html text/markdown registration.
The overlap between these Markdown formats is actually larger than with many other formats. Possibly even larger than HTML’s overlap back when MS Explorer was the dominant browser.
No way. You were never left in doubt about whether a normal HTML tag would work, or whether tables were available or would become a jumbled illegible mess, or whether a line break in the source would become a space or a hard break. And that’s just the first three things that occur to me.
Re: How Markdown took over the world
#253The writeup does not mention Jeff Atwood (Stackoverflow founder) trying to convince Gruber to standardize markdown. Atwood approached him publicly in a series of blog posts, but Gruber kept silent, and if I remember correctly finally declined stating that he didn't want to spend time jumping through other persons' hoops. Although it sucks that markdown is not standardized, I still see this as an inspiring example of…
It happened a bit differently; Atwood and friends simply came out with a standard document and called it "standard markdown", which Gruber then refused to endorse. Eventually after the series of blog posts and some back and forth they renamed the project "CommonMark", which it is still called today. I am not sure (of course), but I think Atwood simply thought standardizing this format was so obviously valuable that h…
Re: How Markdown took over the world
#254The writeup does not mention Jeff Atwood (Stackoverflow founder) trying to convince Gruber to standardize markdown. Atwood approached him publicly in a series of blog posts, but Gruber kept silent, and if I remember correctly finally declined stating that he didn't want to spend time jumping through other persons' hoops. Although it sucks that markdown is not standardized, I still see this as an inspiring example of…
It happened a bit differently; Atwood and friends simply came out with a standard document and called it "standard markdown", which Gruber then refused to endorse. Eventually after the series of blog posts and some back and forth they renamed the project "CommonMark", which it is still called today. I am not sure (of course), but I think Atwood simply thought standardizing this format was so obviously valuable that h…
https://blog.codinghorror.com/standard-markdown-is-now-commo...
And an interesting discussion on hn about it: https://news.ycombinator.com/item?id=4700383
Re: How Markdown took over the world
#255I love Markdown. My favorite Markdown creation was "GistDeck", a bookmarklet that turned a GitHub Gist of Markdown content into a slide show. So much easier to make and share than a PowerPoint deck. https://github.com/nzoschke/gistdeck
Broken homepage
Re: How Markdown took over the world
#256Re: How Markdown took over the world
#257Earlier quoted context omitted.
A more intuitive norm, used in other formats, would have been : *bold* /italics/ _underline_
That's exactly what we used in on usenet (except,without rendering unless you were using a nice GUI reader, not just tin/rtin) The problem is that that's too many characters to reserve (they all have to be escaped when you want the actual character) making the resulting text look awful in plain text mode.
So *this* and /that/ express formatting, but not 4 * 5 nor 4*5 nor 4/5 nor m/s.
Re: How Markdown took over the world
#258Earlier quoted context omitted.
I don’t follow. Marked definitely isn’t a programming tool. There’s nothing about Markdown that says nested lists should look like code. That’s just an accident of whatever editor you might be using, not of others.
> There’s nothing about Markdown that says nested lists should look like code. Yes there is. The Common Mark spec, from 2014, says 4+ spaces indents are code. Nested lists go beyond 4+ indents pretty fast.
Also, note that CommonMark is not identical to Markdown. It intends to be a standard definition of the language, but may differ from the original definition and implementation.
Re: How Markdown took over the world
#259It would be insanely faster to render
Re: How Markdown took over the world
#260> ...that it was too difficult or inconvenient to write out full HTML by hand It's not necessarily that writing HTML or other markup flavors is harder (obviously it is), but the beauty of Markdown for me is that it's perfectly readable in its raw form as well as with an applied styling. And speaking of customizing the 'look' of markdown, a shameless plug for a markdown editor I've been working on with extensive custo…
Off-topic a little bit, but some feedback for your editor: I saw Kraa when you posted it here on HN, and decided to give it another go, even though I remembered that I dismissed it quickly the first time. I only got shy beyond the first line -- Kraa breaks words anywhere to wrap to the next line, really a no go for me, at least in Markdown (it's different if I enable word-wrap in my code editor). Played around a litt…
- An option to render markdown syntax vs immediate translation is coming
- The horrendous bug around word-wrap (in firefox only) should be fixed within days
- adding [ ] for tasks as an alt to [].
As for changing paragraph style, this is purposefully 'hidden' inside the leaf settings (with tons of customization options for everything, not just paragraphs).