3 ms·
Surely "How Not To..." is typically used when you're talking of a bad way to do something, or a way to fail - so this sounds like it's describing a bad way to r
by cannam 7y ago
Surely "How Not To..." is typically used when you're talking of a bad way to do something, or a way to fail - so this sounds like it's describing a bad way to rewrite something in Rust, which is not the case.
It also isn't the wording used in the original article title.
- steveklabnik 7y ago> so this sounds like it's describing a bad way to rewrite something in Rust, which is not the case. I think this kind of title is trying to do exactly that, or at least, that's how I took it. > It also isn't the wording used in the original article title. This is a good reason to switch it, for sure. I didn't realize this, if you had led with that, I wouldn't have said anything :)
- lmkg 7y ago> I think this kind of title is trying to do exactly that, or at least, that's how I took it I took the exact opposite: This article is describing an alternative to RiiR, so that RiiR is avoided when not needed.
- steveklabnik 7y agoI don't disagree with you is that the thesis of the article is "don't re-write something in Rust." What I was trying to say is that I think the title is making a joke; it's saying "how to re-write something in Rust badly", because well, it's not re-writing it in Rust at all.
- aidenn0 7y agoI thought the title was making a joke, but then I read the article and IMO the actual article title of "How to not RiiR" is much more indicative of it's content than the HN title of "How Not to RiiR"
- coldtea 7y ago>so this sounds like it's describing a bad way to rewrite something in Rust, which is not the case. Actually, this is the case. It describes the bad way (and bad reasons) to rewrite something in Rust.