Live data from Hacker News

Shrimple – A Simpler, Nicer Markdown

qount25.dev

21–30 of 43 posts

Re: Shrimple – A Simpler, Nicer Markdown

#21
post #14
post #11

> a better, cleaner Markdown alternative What makes it better or cleaner? It isn't explained anywhere on the page. It looks about the same as markdown to me.

It looks slightly worse to me. Slightly worse and not even ubiquitous? [Edit:] There's h1 and h2, who'd ever need h3? You gotta be kidding me!

Lol, I have personally written docs down to at least h4-5

Re: Shrimple – A Simpler, Nicer Markdown

#22

How is it more convenient to add lines under a title than start with a # ? How is it better to limit to h1 and h2 only?

I sort of lament the use of lines under headings, as they look visually better for human readers of Markdown, but they're worse in other ways: ambiguous heading levels (quick, which is h2, `===` or `---`?), and less token-efficient.

For me, the use of indentation over ``` for code blocks is a complete non-starter, though. It's hostile to copy-and-paste.

Re: Shrimple – A Simpler, Nicer Markdown

#25
post #22

How is it more convenient to add lines under a title than start with a # ? How is it better to limit to h1 and h2 only?

I sort of lament the use of lines under headings, as they look visually better for human readers of Markdown, but they're worse in other ways: ambiguous heading levels (quick, which is h2, `===` or `---`?), and less token-efficient. For me, the use of indentation over ``` for code blocks is a complete non-starter, though. It's hostile to copy-and-paste.

> I sort of lament the use of lines under headings, as they look visually better for human readers of Markdown

Maybe I am spoiled but I rarely read markdown directly. As a user of vscode I do ctrl + shift + v on a markdown file and read the rendered version.

Re: Shrimple – A Simpler, Nicer Markdown

#28
post #18

About five years ago I faced the fact no two Markdown implementations are fully compatible. I made StrictMark[1], which is a backwards-compatible Markdown dialect with a formal grammar (I use Ragel for parser generation btw). Takes 5-10 min with LLMs to make any implementation, cause formal grammar is unchanged. I use it, no one else does, which is not an issue cause it is backwards-compatible. GitHub renders it fine…

How does it compare to CommonMark, which I think was the first formally specified Markdown dialect?
Post reply on HN