Hacker News Reader

Comment by alain_gilbert | Hacker News Reader

Should add "rust" in the title, so that we know what the article is talking about.

If you're one of the "rust/go in title" haters... please go rage somewhere else.

This is literally the worst post title I've ever seen on HN :D

The corresponding rule is worded so harshly that I’m not surprised the poster didn’t dare to change it ( https://news.ycombinator.com/newsguidelines.html).

Not merely worded but also enforced that way.

That’s not true. The moderators accept suggestions and changes titles to something other than the original time and again. It is a guideline after all, it depends on context. I have zero doubts a more descriptive title would be accepted in this instance, as long as it were accurate and not clickbait.

https://hn.algolia.com/?query=by%3Adang%20change%20title&sor...

I've seen many cases of useful descriptive titles being switched to uninformative ones (Stephen Hawking's thesis is one that immediately comes to mind). Every title edit that I've seen in realtime has looked like a robotic replacement with the page title. (Perhaps whatever moderators are active in my timezone are less flexible about their guidelines than dang is)

At least it was a pleasant surprise that it’s not about the Humane AI Pin.

I'd already forgotten about that thing...!

> The Pin type (and the concept of pinning in general) is a foundational building block on which the rest of the the Rust async ecosystem stands.

Was this not the first sentence of the article when you wrote this?

It's about beeing able to quickly scan titles and decide if it's worth clicking on. If all titles were similar, we would spend a lot of time clicking each link to see if it is relevant.

It does indeed have nothing to do with boats.

But it also has everything to do withoutboats.

Why would anyone hate that? It’s a good marker, like [video], that tells folks like me not to bother clicking.

It’s against the rules for one

The “rules” are guidelines. Good titles should be useful and encourage those interested to read and do a service to those not interested by preemptively not wasting their time. Consider the following guidelines:

> Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize.

> If you submit a video or pdf, please warn us by appending [video] or [pdf] to the title.

I don’t want a video so this is a good warning. “I wrote hello in rust” is not an article I want to read. “Type erasure in rust” could be an article I might click on.

The title “Pin” is so meaningless it’s like clickbait: someone might waste their time clicking on it and be annoyed, especially if they read synchronously (I just open a bunch of tabs in background in a single pass so it’s not as bad for me).

In this case I clicked the comments first to see what would happen if I were to click on the article. During the week I’d just skip it.

Yesterday there was a link to a tweet, so the title had to be made up. It could have been “Biden drops out” (people have lots of context) but was “Joe Biden stands down as Democratic candidate”. Just “Biden” would have been clickbait.

Even if you claim it's a guidelines, it's enforced like a rule

Not in my experience, but YMMV

I've seen a decent amount of people that blacklist keywords like rust, blazingly, etc.

Which makes some sense if rust is only of tangential concern...

"I build cool thing X in rust applause" sucks and is borderline spammy imo

But when discussing a language feature, a type, including the language name should be a given and not trigger any rust haters

I was disappointed not to see Intel Pin (https://www.intel.com/content/www/us/en/developer/articles/t...)

Reply on news.ycombinator.com