Earlier quoted context omitted.
I'm seeing lots of bots/agents misusing backticks like this. It's because people are writing agent plans in markdown and the agent thinks it's appropriate everywhere. Maybe you shouldn't be running all your comment replies through Claude.
Dude people have been doing this since long before LLMs. It's more an artifact of Slack than anything.
Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
81–85 of 85 posts
Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#82Earlier quoted context omitted.
I'm seeing lots of bots/agents misusing backticks like this. It's because people are writing agent plans in markdown and the agent thinks it's appropriate everywhere. Maybe you shouldn't be running all your comment replies through Claude.
what are you talking about
Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#83Earlier quoted context omitted.
what are you talking about
Backticks ` ` are used to trigger code-style formatting in markdown. Since all the coding AIs are trained almost entirely on github, you see it everywhere in their output. They'll use it even in places where it's supposed to be just plain text, and almost always in git log messages, which by spec have no formatting.
HN itself renders * as emphasis, but not ` for "code"; this doesn't mean HN is a broken markdown machine or that i'm a bot. many hn comments use plain text conventions for links, see examples that use footnote style markdown-like links[0], I was [doing markdown links here back in 2017](https://news.ycombinator.com/item?id=14763397) even though they've never been parsed by HN.
This kind of semantic formalism in text goes way back, its not so different from something like Chicago style citations first published in 1906 [1].
[0]: https://news.ycombinator.com/item?id=47258996
[1]: https://www.chicagomanualofstyle.org/dam/jcr:bba47b07-61ba-4...
Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#84Re: Show HN: Nub – A Bun-like all-in-one toolkit for Node.js
#85(1) adopts existing tech and improves, rather than a greenfield project with worse compat
(2) the way it uses existing node mechanisms to implement itself (+oxc) is very smart
(3) i like that the node.js-forever crowd has a way to use the newest stuff