News for hackers. Stuff that matters.
Re:Htmlq: like jq, but for html by cyberge99 on Tuesday September 07, 2021 @11:05AM (#28445755)
I believe he tailored it to his target audience. If you find it confusing, you are likely not it.
Re:Htmlq: like jq, but for html by ritchiea on Tuesday September 07, 2021 @11:17AM (#28445901)
As web developer for over a decade "bits content" doesn't mean anything to me. But I understand what the tool does from the rest of the description. Try running a google search for "bits content," [0] it's not a commonly used phrase in web development or anything. It's a poor choice of words.

0. https://www.google.com/search?hl=en&q=%22bits%20content%22

Re:Htmlq: like jq, but for html by chownie on Tuesday September 07, 2021 @11:25AM (#28445978)
It's supposed to be "bits of content", it's not jargon. The author's just accidentally a word, we all do it.
Re:Htmlq: like jq, but for html by ritchiea on Tuesday September 07, 2021 @11:29AM (#28446025)
It's more than fair to say in technical documentation you intend others to use having a grammatical error or missing word is confusing and a problem. It's the writing equivalent of having a bug in your code. And it's definitely not "writing to a target audience" as the parent comment suggested. We all make mistakes but don't try to call a mistake effective documentation.
Re:Htmlq: like jq, but for html by RobertKerans on Tuesday September 07, 2021 @11:55AM (#28446272)
Of course it is, but neither parent nor anyone else is saying anything close to the mistake being effective documentation. There's a single missing word which needs to be added in, but the overall text is clearly writing to a target audience. You are aware of this, and of how small the mistake is, and you understand what the sentence should read as, so I'm not sure what your point is?