Live data from Hacker News

The Curse of Markdown

codehike.org

11–20 of 120 posts

Re: The Curse of Markdown

#11

Non-related, but this is the first time I actually like animations that happen while scrolling. I think it has something to do with the fact that I still have control over the scroll on the right.

Yes, this one doesn't hijack the scroll. It just reacts to it, by changing the text formatting.

I still didn't like it. But it's undeniably much better than the usual way people animate their sites.

Re: The Curse of Markdown

#13

There's a special circle of hell for places who make "plot-like" illustrations that are supposed to look like data visualisations but are just graphics. It's extremely deceptive. TFA has a bunch of things which look like plots of richness vs cost but are actually just what a statistician would call "totally made-up bullshit"

"There is a relation, and it should look like this" is a very common way for people to express themselves.

Your way would ban all the engineerings and most of physics from being created.

Re: The Curse of Markdown

#14
“I have created a tool, and I’m imagining that it’s very important. Just look at this data I made up!” What a joke.

I think the author forgot to think about the content and got all invested in the display of their site. Should have just used markdown and spent the saved time looking for actual real data.

Re: The Curse of Markdown

#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 images. You can append ".text" to any of his blog article to get the Markdown source; example https://daringfireball.net/2020/10/the_iphone_12_and_iphone_...

Re: The Curse of Markdown

#17

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 is so unnecessary and distracting. I quit reading after the first scroll as my eyes were pulled away from the text.

Re: The Curse of Markdown

#19
Almost all of the blog posts and articles I write nowadays are in Markdown, and it sure is painful sometimes when you need formatting that you just need a liiiitle bit of tweaking to get right.

My solution is to fork the markdown tool I use to add my own tweaks. Some of the changes I added are:

- Vertical padding: Typically, `---` and `*` get converted to `` tags. I use `*` for `` that has different padding top/bottom.

- Code examples with syntax highlighting.

- Block quotes with class names: `> {.warning}`

- Headers and table rows with support for setting a specific anchor ID: `# Header {#myId}`

- `` tags with CSS URL matching to apply certain styles. For example, match `` tags URLs ending with `#screenshot` will have drop shadow.

Post reply on HN