Live data from Hacker News

The Curse of Markdown

codehike.org

31–40 of 120 posts

Re: The Curse of Markdown

#31
> This jump in cost disrupts the trade-off between richness and effort. For content with a sweet spot just beyond Markdown’s limits, the additional effort often seems too high for the small gain in richness, leading to a preference for staying with Markdown and sacrificing richness.

Why is asciidoc not more popular? It seems to support more than markdown and seems straightforward.

Re: The Curse of Markdown

#32

This format—with each paragraph fading as you scroll, and large changing images alongside—is borderline unreadable. Somewhat ironic in a blog post that (I think) is about tradeoffs between text and formatting.

It's a slideshow. I actually kinda like it.

Re: The Curse of Markdown

#33
This would be a much better article if two things changed: One, skip the scroll gimmick. It's a waste of time and space (and that has been discussed enough)

Two, give us examples that live in that supposed wasteland. Without those, it looks like you're building a technology in the abstract. And, don't get me wrong, it's cool tech. It so tickles my sense of "fun engineering challenge, great way to express structure". But I've long learned that means it's also very likely in the "overengineered" corner.

I share your belief that there's a "there" there. (I'm on my umpteenth iteration of my own personal markdown, so I would ;) I think it'd be helpful to crystallize that into more concrete uses.

Re: The Curse of Markdown

#35
I really like the format. The problem with slideshows is you either have to scroll back and forth or click on the next page buttons. This page fixes both of them. Although I can see how the fading out of the text is a bit annoying.

Also is anyone building websites with markdown? I thought it was just a tool to format notes and blog posts. And even then you can insert HTML in it.

Re: The Curse of Markdown

#36

This format—with each paragraph fading as you scroll, and large changing images alongside—is borderline unreadable. Somewhat ironic in a blog post that (I think) is about tradeoffs between text and formatting.

All that work to animate the little bits of data on the canvas, but greying the text was so irritating I closed the page. You don't realize how often your eyes jump back to previous sections until that ability is taken away from you.

It seems like they wanted to make sure the reader knew which paragraph corresponded to the current version of the image/plot. Maybe they could've gotten the effect they were after by setting a border or background on the presently relevant paragraphs.

Re: The Curse of Markdown

#37

This format—with each paragraph fading as you scroll, and large changing images alongside—is borderline unreadable. Somewhat ironic in a blog post that (I think) is about tradeoffs between text and formatting.

It's a slideshow. I actually kinda like it.

Even in slideshow format there's no need for this distracting nonsense. Something like https://idlewords.com/talks/our_comrade_the_electron.htm is perfectly fine.

Re: The Curse of Markdown

#38
post #26
post #16

Markdown has always supported direct raw HTML in it. I don't see any gulf or sudden jump in cost. Don't be a Markdown purist. Even John Gruber, the creator of Markdown, is not a Markdown purist. Go look at the Markdown source of his blog and you will see that he frequently just uses raw HTML. He doesn't even do multi-paragraph ordered lists in Markdown, and chooses to write instead. And he also uses for clickable ima…

On the note of embedding HTML in Markdown, I think it'd be cool if it were just as easy to embed Markdown in HTML. Something akin to a tag. Markdown makes it easy to write formatted content at the cost of initial compiler setup, HTML is 0-cost setup but takes some effort to write formatted content. With a tag one could start with vanilla HTML at zero cost, use all its features straight away, but not have to type HTML…

That sounds like a good idea, until you remember that there is no officially agreed upon markdown spec. For content authors it'd be both fantastic if browsers could just go "you guys go fight it out, we're just gonna go with GitHub flavored markdown" but at the same time for browser makers that's taking a position on something that they have no stake in.

So writing or using someone else's custom element is pretty much your only option here.

Re: The Curse of Markdown

#40

This format—with each paragraph fading as you scroll, and large changing images alongside—is borderline unreadable. Somewhat ironic in a blog post that (I think) is about tradeoffs between text and formatting.

On top of that, the content itself—a spectrum of lean to rich—isn't all that informative, especially compared to its solemn presentation as the result of some kind of deep meditation.
Post reply on HN